Justine Smithies
I think in my #vi journey on #OpenBSD that I'm leaning towards #nvi as in nvi2. Only because I do use some nerd font stuff to pretty up some of my menus and my bar. But obviously that could change as I may get rid of those nerd fonts and just stick with plain text?
If you're an OpenBSD user and use vi instead of vim do you use the builtin n(vi) or nvi2 ?

https://github.com/lichray/nvi2
GitHub - lichray/nvi2: A multibyte fork of the nvi editor for BSD

A multibyte fork of the nvi editor for BSD. Contribute to lichray/nvi2 development by creating an account on GitHub.

GitHub
Mar 29 at 1:16pmWeb
Show threadCraig BrozefskyMar 29

@justine i use the built in, but I also only use vi for admin tasks and simple edits. Beyond that, i end up in emacs and was never happy with nvim/tmux when fully kitted out as a terminal coding or doc writing environment.

Maybe you can relate, but I find a conflict between my drive for minimalism and simplicity in the composition of the system, and my direct appreciation of the system as a daily driver — how it makes me feel when I first sit down to work, and how it feels in hour 8 of work.

I found that prioritizing feel over minimalism and simplicity just a bit — keeps me happy

Show threadnmMar 29

@justine I've stuck with the built-in vi on OpenBSD for most tasks. I miss some vim-isms (especially things like ci") but I don't think nvi2 would help with that.

I'd like to use emacs more (heathen) but I find that I end up tinkering with my setup more than doing productive work. The only time I've bemoaned the built-in's lack of utf-8 support was when I tried futzing around with my .XCompose file, but ibus has been a buggy pain in the ass, so even that's not much of a loss.

Show threadromanMar 29
@[email protected] i decided to go with #openbsd builtin vi, but i understand it doesn't work for everyone.
Show threadRuss SharekMar 29

@hi @justine

I've got both installed, but am leaning on trying to use the vi in base.

Show threadnathanaelMar 29
nvi2 because of umlauts
Show threadromanMar 29
@[email protected] how do you type them in?
Show threadnathanaelMar 29
pressing a key on my swiss keyboard ;)
Show threadromanMar 29
@[email protected] oh right! :)
Show threadAntonyMar 29
@justine For quick edits, base nvi is enough for me. I switch to Emacs for heavier work or prose (where I need Unicode occasionally), but if I was without Emacs then nvi2 would work just fine. I've kicked the tyres a little (debating a move myself) and I like it.
Show threadMischa 🐡😎Mar 29
@justine mainly vi in base and nvi2 when specific characters are needed.
Show threadTim ChaseMar 29

@justine

I don't use nvi2, but use a mix of stock vi, stock ed(1), and vim depending on the task.

Show threadPaul SomeoneElseMar 29
I use the builtin vi and love it. It has a few updates that nvi
doesn't have. I have yet to need to type unicode, but I
know that if/when i do, i will need to use nvi2 or maybe
vis. I do keep my eye on editors and also am pretty good
with emacs so I am not worried. but surprisingly
OpenBSD's builtin vi has yet to let me down :)