I don’t do a lot of text editing in terminal, but I used to have to at my last job and I always reached for nano and gave instructions fot nano since it’s just pick up and use.
I was using vim for the first time the other day and I was running through the built in vimtutor. I got a call from a friend and they asked what I was up to, and I said I was doing a tutorial for a text editor. At that moment, I felt simultaneously very silly and very smart.
Well yeah, I’d say the same concept applies to using anything tech related these days. It’d be like if you “knew” where all of the keys on a keyboard layout that you don’t normally use are located - you’d still need muscle memory to actually use it efficiently.
Yeah, again, I don’t do much terminal text editing. I have an IDE. If I’m trying to help someone across the country 1000 miles away fix something on the machine I develop for, I’m going to give them instructions on something that will be incredibly easy to use. I don’t want to have to explain why the arrow keys aren’t working and why they have to use jkl; to navigate or explain how enter edit mode or how so save and exit. Keep it simple stupid.
I don’t do a lot of text editing in terminal, but I used to have to at my last job and I always reached for nano and gave instructions fot nano since it’s just pick up and use.
Nano just feels sluggish as soon as you know vim keybindings. Emacs is a bit overkill for some quck edits, but nano is just to basic
deleted by creator
As a nanoite who couldn’t be bothered to learn editor commands, I switched to turbo, which is essentially a linux port of the DOS text editor
Huh, interesting!
I was using vim for the first time the other day and I was running through the built in vimtutor. I got a call from a friend and they asked what I was up to, and I said I was doing a tutorial for a text editor. At that moment, I felt simultaneously very silly and very smart.
By “as soon as you know” you mean “as soon as you have put those bindings to muscle memory”. Knowing them isn’t really enough.
Well yeah, I’d say the same concept applies to using anything tech related these days. It’d be like if you “knew” where all of the keys on a keyboard layout that you don’t normally use are located - you’d still need muscle memory to actually use it efficiently.
Yeah, again, I don’t do much terminal text editing. I have an IDE. If I’m trying to help someone across the country 1000 miles away fix something on the machine I develop for, I’m going to give them instructions on something that will be incredibly easy to use. I don’t want to have to explain why the arrow keys aren’t working and why they have to use jkl; to navigate or explain how enter edit mode or how so save and exit. Keep it simple stupid.