>>105839282 (OP)
i like nano, its my go to for whatever edits tho for longer sessions i think i want a better tool. nano has its role as the first thing you use to view something and then jumping into whatever else for deeper work
>>105845700
It might be different on GNU+Linux, but the shortcut for the help buffer is on the bottom unless you hid it using the config or commandline argument.
Ctrl + G to show the help buffer.
There are even versions or configs/patches where you can use Ctrl+C & Ctrl+V & Ctrl+X, even the mouse.
>>105845691 >Nano is a lot more user friendly >look inside >tfw had to google how to exit vim >tfw had to google how to select multiple lines or to delete whole line in nano
>>105845831
Maybe you opened Vi instead. That is a terrible experience if you aren't ready for it. There is nothing wrong with preferring mouse/featherpad.
>>105839282 (OP)
It's OK for quick container edits, but unironically harder to use than Vim nowadays. Cause it sits on this obnoxious middle ground, uncanny valley of the standard CUE keybinds, and ^X doesn't actually cut text, nor ^V actually pastes it. So it's way too similar to other text editors except for the last 10% deal breaker bits. Vim's motions (the basic ones at least) are so completely different to anything else that they get burned in your brain once yout commit to it.
Anyone here uses mcedit as their main editor? Altough I've used NC in the DOS days it seems pretty bad compared to nano, but some of my friends swear by it.