R.L. Dane 
π΅ 
C'mon #vim folk, REPRESENT!!
Couldn't seem to get #VimClassic to compile on #FreeBSD.
But then I realized the only thing I used it for is sncli, because it does something funny with the terminal when it hands it off to nvi, such that the cursor becomes invisible. But then, it's just a !reset to fix it, so I might as well just stick with nvi. ;)
JdeBPFun fact: The :x command was added to ex/vi in 1980 because :wq did too much. Horton copied the name from hed.
nvi of course, as you know.
The problem with #nvi's manual is that it is employing two different uses of []. For [Ee] it's doing the conventional set of characters to match thing, as the commands are actually Ex and ex, for everything else [] is indicating an optional string, not a set at all. [Ee][dit] on the line above is an even worse example.
Amusingly: For genuine Joy+Horton #vi, not only is all this on the ex(1) manual page instead, but it is a lot clearer, in part because actual vi doesn't support uppercasing its ex command to Ex.
https://illumos.org/man/1HAS/ex#additional-ex-command-arguments
My .exrc so far:
set ruler
set autoindent
set shiftwidth=4
set iclower
set showmode
set tildeop
set verbose showmode
"(the parts in [brackets] are what you have to type into the editor to
" recreate it)
map gg 1G
map q :q
map [ctrl+v, ctrl+o] :!clear; less --wordwrap %[ctrl+v, enter]
map [ctrl+v, ctrl+s] :w
map :less :!clear; less --wordwrap %[ctrl+v, enter]
map :spell :w !bspell
map Y y$
map :wrap :set noleftright
map :nowrap :set leftright
map :set[ctrl+v, ctrl+v] nowrap :set leftright
map :set[ctrl+v, ctrl+v] wrap :set noleftright
" make ` work like ~ does by default, toggling the case of a single character (I typically use ', so I don't need ` for accessing marks)
map ` ~l
Created my own "brute force" version of bsdspell for my linux boxen for use with #ed and #vi / #nvi. It takes a couple seconds to run, but considering there's 123,985 words in the words file on this linux box, that's not too bad. ;)
https://codeberg.org/rldane/scripts/src/branch/main/bfspell
cc: @gumnos
New #blog #post: Vim Carnival Entry: "The Motion that Changed Everything."
https://rldane.space/vim-carnival-entry-the-motion-that-changed-everything.html
1224 words
cc: my wonderful #chorus: @joel @dm @sotolf @thedoctor @pixx @orbitalmartian @adamsdesk @krafter @roguefoam @clayton @giantspacesquid @Twizzay @stfn
(I will happily add/remove you from the chorus upon request! :)
Thanks to @hyde for the blog concept, and immediate apologies if you get trapped in a #hellthread! π
#rlDaneWriting #blost #vi #vim #nvi #editor #VimCarnival #TheMotionThatChangedEverything #modal #ADHD
Jason Bowen πΊπ¦@rl_dane @ed1conf @mwl
I love his style of writing as well!
Where there's a lineage or evolution, I really like to start as close to the origin as possible (or at least read about it). It gives context for what's come after and I find gives me a better intuition for things.
I'm looking forward to any future posts as you're using ed(1) and it's descendents :)
Is there a solid book or PDF guide I can get on (traditional) vi?
I'm finding the manpages... terse. π«
* manPAGES, as in, I'm consulting different ones
UPDATE: many solid suggestions in the thread. Thanks to all, including the ones that told me about it a month ago and I completely forgot, 'cuz #ADHD go BRRRR! π€£