Editing the scheme language racket in the editor neovim,
$ vi file.txt
:wq
) for write the current file and quit.Your experience is about as long as mine, Mr. Bsz., and a bit more modern, since I retired from the IT biz in 2017. Tinkering with computers is just a hobby for me now.To survive as a developer with some sys admin duties today, you need to know how to use vi (or vim) well enough to do simple modifications to a short file. That's because while installing or maintaining a system, sometime you find yourself in a situation where you have only vi(m) available, and nothing else.
Until a few months ago, I would have said that you also need to know at least one powerful coding editor (text editor) really well; whether that's vim or emacs is not important, as most environments provide both. The reason for that is two-fold: First, sometime you had to work on machines and code bases where only CLI access is available. And GUI-based editors were not good enough to be universally accepted.
However, these days I know there are environments with good GUI-based coding editors, and no need to work via ssh. And when I say "good", I mean: really really good, so good that dozens of very experienced developers prefer to use them over CLI-based tools. Since I've used Unix only for 37 years, I don't know whether I count as "experienced". So today, it is possible to be a serious developer using GUI-based tools only (most of them actually run in web browsers today, that having become the lingua franca of GUI development).
Having said that: Those GUI-based editors still have lots of useful keyboard shortcuts. And the ones I know can all be configured for either emacs or vim mode. So learning one of those editor's user interfaces (keyboard commands) well is going to enhance productivity, even if we are now in a world where there are alternatives to these text-based editors.
# save the file and exit
That might be enough to get you through an emergency.
- press esc to return to normal mode and enter :wq to save and quit or :q! to quit without saving
<nitpick> please supply an example of upper case numbers, WITHOUT referencing xkcd. </nitpick>followed by a letter, followed by a lower case number,
For me I have servers without any GUI installed; I work on client machines with a GUI and a terminal/console and ssh in to the servers and tweak code in vim and refresh the browser on the GUI machine.
Works for me, but there’s plenty of ways to do things!
UPPER CASE: I, II, III, IV, ETC. ...<nitpick> please supply an example of upper case numbers, WITHOUT referencing xkcd. </nitpick>
Wait.... there's servers with a GUI?