which I don’t need my three year computer science degree for.
vi really isn’t complex.
CUA editors
CUA editors work as long as there is grid display and ANSI input. They do not work in a line feed or console-line environment like telnet, console, etc., hence the need for hjkl movement.
Also CUA is an IBM initiative, it wasn’t followed everywhere.
Totally fair, I only learned because I was forced to.
Why wouldn’t it work over telnet when it works via SSH?
Serial consoles feed back information one line at a time, so no curses interfaces. No arrow keys, just hjkl. Anything that needs to count characters and columns (like position-based cursor editors like nano) won’t work over telnet.
in my console, or rather terminal
A serial console and a terminal aren’t the same thing.
vi really isn’t complex.
CUA editors work as long as there is grid display and ANSI input. They do not work in a line feed or console-line environment like telnet, console, etc., hence the need for hjkl movement.
Also CUA is an IBM initiative, it wasn’t followed everywhere.
Vi is unintuitive and annoying to me. Others can use whatever they want but I can’t stand people who tell others they’re wrong for not preferring vi.
I use micro in my console, or rather terminal. Why wouldn’t it work over telnet when it works via SSH?
Totally fair, I only learned because I was forced to.
Serial consoles feed back information one line at a time, so no curses interfaces. No arrow keys, just hjkl. Anything that needs to count characters and columns (like position-based cursor editors like nano) won’t work over telnet.
A serial console and a terminal aren’t the same thing.
If you like micro, use micro. I don’t care.
I just boot straight into eMacs.
Emacs is a stranger breed of ppl than vi users still… Kudos.
CUA was not followed everywhere, but it was followed by CDE and so it was native to Solaris.
Yes, well CDE doesn’t enter into the equation over a minicom console. As I said, cua isn’t super useful in line-feed environments.
I haven’t seen CDE in over 20yrs.