Live data from Hacker News

The vi family

lpar.ath0.com

151–160 of 198 posts

Re: The vi family

#151
post #129

Nvi 2 (nvi under openbsd) has Unicode support. It's like BSD Vi but with Iconv. Perfect for my needs. On graphical Vis, I liked Cream, which almost made Vim seamless. https://cream.sourceforge.net/ Instead of GTK2/3, I prefer Athena Vim.

> Nvi 2 (nvi under openbsd) has Unicode support. It's like BSD Vi but with Iconv. Perfect for my needs.

My primary editor for text (not code) editing and e-mail. I just wish Unicode support made it into base vi(1) on OpenBSD, but for now I can at least use it for all other purposes other than the ones in the previous sentence.

Re: The vi family

#153

I have nothing against Vi or Emacs, but since I strongly prefer GUI and mouse over terminal I use GUI editors. When I don't have a GUI available, I use micro, nano, joe.

Maybe try emacs if you haven't. It is primarily a GUI editor

Re: The vi family

#154

Earlier quoted context omitted.

Yes, it almost feels like inserting politics to an otherwise apolitical discussion. Just unnecessarily charges the discussion and makes one not want to engage with the article.

you keep using that word, 'apolitical', i do not think it means what you think it means

I only used it once.

Re: The vi family

#155
post #143

Earlier quoted context omitted.

allow me to quote the Ancients, the vi creator himself: > What would you do differently? > JOY: I wish we hadn't used all the keys on the keyboard. > ... > JOY: The fundamental problem with vi is that it doesn't have a mouse and therefore you've got all these commands. In some sense, its backwards from the kind of thing you'd get from a mouse-oriented thing. > Its like one of those pinatas - things that have candy in…

> The fundamental problem with vi is that it doesn't have a mouse The fundamental advantage of vi is that it doesn't have a mouse. If you were born with three arms you can go for sam or something.

I think one of those early thinkpad keyboards is ideal. You can use the mouse without leaving home row. I wish there was a nice mechanical keyboard with a thinkpad nipple

Re: The vi family

#156
post #119

I’ve been a long time vim user, and I honestly never really bought into the efficiency claims. That gets repeated over and over, but If you’re a slow typer then no editor can really make much of a difference, and development in reality is a lot of reading code and thinking about code when it comes down to it. I’ve never used it because I thought it would make me some lightning fast super developer. I’ve always used i…

It is fun because it is fluent. vi has a language.

If I spend more than a couple minutes in an arrow-keys-and-mouse text editor, I often find myself unconsciously reverting to vi-language and getting confused. "Oh, I want to go change that sentence up the page that starts with 'Looking at...'" so I type "?Looking at" into the text editor and then stare at it for a few seconds before hitting backspace and reaching for the mouse like a caveman.

Re: The vi family

#158
post #32

Earlier quoted context omitted.

I never edited the default config much. But then I discovered https://www.lazyvim.org/ . Turns your copy of NeoVim into an IDE. I still haven't edited the default config much, actually. But now I'm probably 2x to 3x as productive in vim (nvim, now) as before. P.S. If you decide to check out the LazyVim config, I highly recommend reading https://lazyvim-ambitious-devs.phillips.codes/ all the way through. There's a lot…

The demos of LazyVim looks really nice, and people seem to get a benefit/joy out of it. I gave it a try, but it's a little to much for me. Right now I think my .vimrc is two lines. That's also sort of silly as I benefit very little from all the things Vim can do.

I am with you on that one. I use Emacs and the Vi family. If I wanted IDE features in my text editor, then I would probably be better served using an IDE. Less to manage is less to burden.

Re: The vi family

#159

Earlier quoted context omitted.

I’ve been a long time vim user, and I honestly never really bought into the efficiency claims. That gets repeated over and over, but If you’re a slow typer then no editor can really make much of a difference. Little by little your movements become more complex and efficient, and the journey to figuring that out is fun and interesting. The slight contradiction in your comment has a lot of truth in it. It’s just fun, a…

> practicing this game makes you better at any number of tasks that are relevant to your daily work. Vi key bindings don't apply outside of vi

That's not true at all. Many readline and terminal based clients support vi bindings, you just have to enable them. e.g. stuff like psql.

The shells themselves also support vi binding.

Outside of the terminal tools like Vimium add support to browsers and many other interfaces.

Re: The vi family

#160
post #151
post #129

Nvi 2 (nvi under openbsd) has Unicode support. It's like BSD Vi but with Iconv. Perfect for my needs. On graphical Vis, I liked Cream, which almost made Vim seamless. https://cream.sourceforge.net/ Instead of GTK2/3, I prefer Athena Vim.

> Nvi 2 (nvi under openbsd) has Unicode support. It's like BSD Vi but with Iconv. Perfect for my needs. My primary editor for text (not code) editing and e-mail. I just wish Unicode support made it into base vi(1) on OpenBSD, but for now I can at least use it for all other purposes other than the ones in the previous sentence.

Ironically ed(1) supports Unicode under X if you XTerm and locale are set for that.
Post reply on HN