Justine Smithies
I've still not given up on #Vi as my editor instead of #Vim and to be perfectly honest, I'm not really missing the fancy Gruvbox theme and Vim's auto-completion. It's making me learn new tricks and stops me relying on the help of plugins. Good for the old grey stuff I'd say! I even changed the 88x31 button on my websites footer from Vim to Vi. #RunBSD #OpenBSD
Apr 1 at 7:46pmWeb
Show threadSijmen 🧑‍💻3d ago

@justine hear hear!

Sadly a plain text editor is usually not suitable for traditionally IDE-heavy languages like Java, but for everything else, vi all the way.

Show threadPedroMJ3d ago
@sjmulder @justine Having well-structured code, one can use vi for a project of any size---I prefer vim, but that's other story. It is generally more productive. Things like auto-completion only add stress ---one has to check that the proposal is fine, but it is faster to write than to read+check. For novices, IDEs help a lot. For seniors, they are
just put in the middle.
Show threadLaurent Cimon3d ago
@justine I prefer nvi2 on FreeBSD to vim, it's simpler and more responsive I think. It gets some getting used to though, things like undo are u followed by . to undo more, then you can press u again followed by . to redo a couple times.
Show threadJustine Smithies3d ago
I use OpenBSD vi which is basically nvi and if I really need Unicode stuff displayed in scripts nvi2. Loving this journey as I stayed away from Vi all these years using Vim and sometimes Neovim. But lately I feel I've been missing out on my education. ;)
Show threadRuss Sharek3d ago

@justine @clf

That's exactly what I've been experiencing in moving from vim to vi. So many basic tasks feel like vim bolted on another way to do them rather than encouraging users to learn shell tools (and in a couple of cases the editor itself).

Show threadThorsten Zöller2d ago

@RussSharek @justine @clf

That's one reason why the often quoted reply https://stackoverflow.com/a/1220118 is so good: It makes it clear that many "features" or "improvements" of Vim are actually not improvements at all, but rather workarounds if one does not properly understand how to do things using what is already given.

One of my favorite examples is visual mode, which I have used for years before I noticed I don't need it at all; I just failed to properly learn the respective ccommands for moving and marking.

Of course, the next logical step after moving from Vim to vi would be to move on to ed 

What is your most productive shortcut with Vim?

I've heard a lot about Vim, both pros and cons. It really seems you should be (as a developer) faster with Vim than with any other editor. I'm using Vim to do some basic stuff and I'm at best 10 ti...

Stack Overflow
Show threaded(1) conference2d ago

@thorstenzoeller @RussSharek @justine @clf

/me doffs hat with a warm smile and welcoming gesture

Show threadRuss Sharek2d ago

@ed1conf @thorstenzoeller @justine @clf

I'm afraid of the nice ed and its simple ways. ;)

Show threadPaul SomeoneElse2d ago
This is really cool hearing from you and others :)
I started when I was convinced by the Golang guy to
give up on syntax highlighting. I was like great I
have wanted to use OpenBSD's vi anyways.
I haven't looked back.

One of the cool things is even if you go back
I bet you will have a lot more of the vi
primitives in your fingers.
Like you can learn ALL of vi.
You can't say that about emacs or vim.
Show threadRuss Sharek2d ago

@pkw @justine

I'm a simple primate and I appreciate simple tools, so the idea of being able to hold something in my limited mind is appealing.