If you are seriously thinking about learning #Vim / #Neovim, do yourself a favor and proceed as follows:
-
If you are seriously thinking about learning #Vim / #Neovim, do yourself a favor and proceed as follows:
1. Grok ed(1).
2. Grok vi(1).
3. Ask yourself whether you really need anything ed(1) and vi(1) don't provide.If your answer to step 3 is "yes", go ahead. But first, do steps 1 and 2.
Here is how to do step 1: Read the man page (it's rather short), read "Ed Mastery" by @mwl (those two steps are interchangeable and even parallelizable), then use it consistently.
Here is how to do step 2: Read the man page (it's rather short as well, though not as short as ed's), then use it consistently.
Also, have a look at https://stackoverflow.com/a/1220118.
-
If you are seriously thinking about learning #Vim / #Neovim, do yourself a favor and proceed as follows:
1. Grok ed(1).
2. Grok vi(1).
3. Ask yourself whether you really need anything ed(1) and vi(1) don't provide.If your answer to step 3 is "yes", go ahead. But first, do steps 1 and 2.
Here is how to do step 1: Read the man page (it's rather short), read "Ed Mastery" by @mwl (those two steps are interchangeable and even parallelizable), then use it consistently.
Here is how to do step 2: Read the man page (it's rather short as well, though not as short as ed's), then use it consistently.
Also, have a look at https://stackoverflow.com/a/1220118.
i wish i'd seen this advice decades ago.
i learned it the hard way—in exactly the wrong order: vim, then vi, then ed/sed...
-
If you are seriously thinking about learning #Vim / #Neovim, do yourself a favor and proceed as follows:
1. Grok ed(1).
2. Grok vi(1).
3. Ask yourself whether you really need anything ed(1) and vi(1) don't provide.If your answer to step 3 is "yes", go ahead. But first, do steps 1 and 2.
Here is how to do step 1: Read the man page (it's rather short), read "Ed Mastery" by @mwl (those two steps are interchangeable and even parallelizable), then use it consistently.
Here is how to do step 2: Read the man page (it's rather short as well, though not as short as ed's), then use it consistently.
Also, have a look at https://stackoverflow.com/a/1220118.
@thorstenzoeller @mwl I learned vi from either a Stephen Kochan Unix book, or Unix for the Impatient.
There's also a nice book on Vim, from long before the slop infestation:
https://pragprog.com/titles/dnvim2/practical-vim-second-edition/
#vi #vim -
If you are seriously thinking about learning #Vim / #Neovim, do yourself a favor and proceed as follows:
1. Grok ed(1).
2. Grok vi(1).
3. Ask yourself whether you really need anything ed(1) and vi(1) don't provide.If your answer to step 3 is "yes", go ahead. But first, do steps 1 and 2.
Here is how to do step 1: Read the man page (it's rather short), read "Ed Mastery" by @mwl (those two steps are interchangeable and even parallelizable), then use it consistently.
Here is how to do step 2: Read the man page (it's rather short as well, though not as short as ed's), then use it consistently.
Also, have a look at https://stackoverflow.com/a/1220118.
@thorstenzoeller I do find LSPs very useful, but the slop going into both vim and neovim has brought me back to vi as often as I can.
-
i wish i'd seen this advice decades ago.
i learned it the hard way—in exactly the wrong order: vim, then vi, then ed/sed...@hi Same here - from Vim to vi to ed. While I do use (Neo)Vim, I am convinced that learning plain vi and ed has improved my way of using "improved" versions of ed/vi.
There is this truly profound core, around which Vim and its decendants have added layers upon layers of functionality (not all of it bad, of course - some of it simply superflous, some of it really good). But it is remarkable how much is contained in this small, beautiful core. And it is just as remarkable how often this core is fully sufficient - we often need way less than we think we do (a very general principle in life...).
-
If you are seriously thinking about learning #Vim / #Neovim, do yourself a favor and proceed as follows:
1. Grok ed(1).
2. Grok vi(1).
3. Ask yourself whether you really need anything ed(1) and vi(1) don't provide.If your answer to step 3 is "yes", go ahead. But first, do steps 1 and 2.
Here is how to do step 1: Read the man page (it's rather short), read "Ed Mastery" by @mwl (those two steps are interchangeable and even parallelizable), then use it consistently.
Here is how to do step 2: Read the man page (it's rather short as well, though not as short as ed's), then use it consistently.
Also, have a look at https://stackoverflow.com/a/1220118.
@thorstenzoeller @mwl Wait, if you're learning ed and vi, you might as well add Emacs to the list.
[Actually, I gave up and just use VSCode now. The 1980s were 40 years ago.]
-
R relay@relay.infosec.exchange shared this topic
