3 ms·
Yeah, for quick edits I prefer nano. Might just be because I grew up with edit on DOS, and Out of the vi, emacs and nano it was the closest and I just stuck wi
by ChrisClark 5y ago
Yeah, for quick edits I prefer nano. Might just be because I grew up with edit on DOS, and Out of the vi, emacs and nano it was the closest and I just stuck with it.
Any programming I do is in Jetbrain IDEs.
But I saw a comment here long ago that says it's worth learning vim keybinds, even if you never use vim. Because you can be sure, no matter what IDE or editor you end up using, someone has created a vim keybinds plugin. You can have the same keybinds across everything.
I've never gotten around to learning though.
- Arnavion 5y agoMeh, that vim keybinds thing is an exaggeration. Using arrows keys for moving the cursor, holding down Ctrl for jumping words, holding down Shift for selection, etc is even more consistent across editors, and doesn't even need any plugins.
- ChrisClark 5y agoI was more thinking of the benefits of vim-style, the advanced controls for moving and jumping around according to code structure. Not just jumping a word at a time, but jumping to a character, deleting a word, sentence, block, etc. Those are not always standardized across editors.
- Arnavion 5y agoDeleting a word - Ctrl-Delete. Deleting a line - Shift-Delete. Jumping to a character, deleting a block - while vim does have bindings for these, I've never found myself using them. For the latter especially, moving to the start of the block and then selecting to the end of the block is better to me just because it lines up with my eyes scanning the thing I'm planning to delete. With vim I would have to pause and double-check what I'm about to delete anyway, and if it doesn't fit in one page I'd have to move around to inspect it anyway.