@arclight This is how I end up with ":q!" in my crontab
Thank the deities for vim!
'vi' was such a bastard to learn in the 90s, that I could never be arsed to go through such pain again, so now I use gvim on my Linux machine at home, and my Windows laptop at work, and have evolved a moderately busy .vimrc config file that works for both. That, plus 14yrs of coding in Perl, mean that I am now the in-house regex guru π
@bytebro I have never really liked using gvim because I normally work in the terminal on remote systems (without X forwarding) and I never really liked how it looked. I try again every couple years, though. Maybe some day.
Everyone's mileage will vary of course, but it's very configurable, to be fair, and I get a perfectly usable interface (I rarely use menus and such in vim) on both platforms. And basic habits I inherited from Win, like Ctrl-C for 'cut', Ctrl-V for 'paste', etc all work as expected on both.
@xinit @bytebro @1000millimeter @arclight @jalefkowit
At work, I use Windows Terminal with Powershell 7 as default terminal application.
Run "winget install vim.vim" to install vim and gVim, and add "C:\Program Files\Vim\vim91" to your Path environment variable.
I feel naked without a sane editor when working in a terminal.
@mjack @xinit @bytebro @1000millimeter @arclight @jalefkowit
I was six years old when vi was invented. Still can't be arsed with it except as a last resort.
Windows is GUI first so why not use that? Win Terminal is pretty decent but why is it restricted to desktop only and not servers?
Notepad++ is hands down the Windows editor for me. It has a follow mode for logs, which is a killer feature for me.
Ideally I avoid Windows but when needs must ...
If you do Windows then embrace it as such. vi is from another world and does not really fit. You might look at micro and tilde instead.
Perhaps your editor choice implies that your OS choice is ill-advised 8)