13 ms·
Nice thing about Nano is that they arrow keys always seem to do what they are supposed to, no matter the system, shell, TTY, etc. Vi seems to have issues someti
by elsurudo 10y ago
Nice thing about Nano is that they arrow keys always seem to do what they are supposed to, no matter the system, shell, TTY, etc. Vi seems to have issues sometimes, and needs extra config
- dozzie 10y agoI don't know about vi (I think it's still rare on Linux systems), but Vim typically does what is expected from it.
- happyslobro 10y agoIf you ever happen to bork your kernel badly enough to prevent it from booting, you'll find a classic VI pretty quickly, and probably be grateful for it.
- dozzie 10y agoWell, not really. My system doesn't have vi installed. Vim, of course, any time of the day. Stripped Vim (vim-tiny, as Debian calls it), sure, just after installation. But vi -- no, I don't have it installed. For quite a long time Linux didn't have vi even ported. There were several clones, like Elvis and nvi (and Vim, of course). Few years ago I learned that somebody took the effort and actually ported traditional vi to Linux. I doubt mainstream distributions cared to include it, though. Why should they? They already have plethora of clones packaged, and those clones typically do much more than traditional vi. The lesson from this tale is this: don't call vi what is merely a vi clone. vi is a name of a quite concrete project. And as for kernel unable to boot: if it can't boot, then how the heck am I supposed to run anything under this kernel? Unless you meant kernel can't run OS from local disk. I know Linux well enough to manage to run my things. You would be surprised how much could you hack through if you knew how ELF binaries work.
- traviscj 10y agoYou are being needlessly pedantic. The point is that typing "vi" into a terminal runs some application that implements a "vi-ish" interface. Whether it is ported vi or vim or vim-tiny has some effect on how nice that interface is to work with, but I would argue that most vim users would be able to get their configuration fixed or whatever
- dozzie 10y ago> You are being needlessly pedantic. I assure you I am not pedantic needlessly. The claim was "vi has some issues with arrow keys". Now tell me: which vi clone was elsurudo talking about? Because those are different projects. And Vim doesn't have a smallest issue with arrow keys (unless with "compatible" option set, I think, but I didn't use it for years and I may remember wrong).
- macintux 10y agoAs a cranky old man, I'd argue all of them that support arrow keys have issues. Arrow keys are an abomination.
- deleted 10y ago[deleted]
- savanaly 10y agoPresumably h, j, k, l will always get you around in vi?
- dwaxe 10y agoj and k behavior may vary depending on your config.
- edanm 10y agoEverything can vary depending on your config, but unless they were explicitly remapped, j and k should pretty much do the same thing everywhere. Have you seen somewhere where that isn't the case?
- zodiac 10y ago> Have you seen somewhere where that isn't the case? I use the dvorak keyboard layout and used to remap (among other things) j and k in vim, since they were not on the home row for me. I stopped doing that after a while though.
- IshKebab 10y agoYeah but that is so much less usable. Quick, which one is up?