From: Andy Kosela <akosela@andykosela.com>
To: Will Senn <will.senn@gmail.com>
Cc: TUHS <tuhs@tuhs.org>
Subject: [TUHS] Re: diving into vi (nvi) - some observations from a slow learner
Date: Fri, 7 Jun 2024 18:58:14 +0200 [thread overview]
Message-ID: <CALMnNGhBsw4t3Bar5JVd_UWjhO2kNMGGrKchMRS8CmFpuhd1Hw@mail.gmail.com> (raw)
In-Reply-To: <05302a0e-58b6-450c-8554-4546a409d603@gmail.com>
[-- Attachment #1: Type: text/plain, Size: 712 bytes --]
On Friday, June 7, 2024, Will Senn <will.senn@gmail.com> wrote:
> Thanks for the tips, Ralph. I definitely learned the 6, but put 'em on a
> card with searching. Here's my motion card, including the scrolling
> commands, mark movement and a couple odd balls, to see how my mind works :)
> :
>
> https://decuser.github.io/assets/img/vi/motions-notecard.jpg
>
>
The best thing about vi/nvi/vim is that you do not need to know all the
arcane commands for it to be usable. You can get along quite happily using
just a small subset of them. The beauty of vi lies in the interface
minimalism and ubiquity.
It is still my favorite editor after all these years and still using it on
Linux/*BSD/MS-DOS/AmigaOS.
--Andy
[-- Attachment #2: Type: text/html, Size: 1059 bytes --]
next prev parent reply other threads:[~2024-06-07 16:58 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-07 14:44 [TUHS] " Will Senn
2024-06-07 15:41 ` [TUHS] " Ralph Corderoy
2024-06-07 16:20 ` Will Senn
2024-06-07 16:58 ` Andy Kosela [this message]
2024-06-07 17:29 ` Marc Rochkind
2024-06-08 4:44 ` Dave Horsfall
2024-06-08 4:50 ` Warner Losh
2024-06-08 6:22 ` Rob Pike
2024-06-07 22:12 ` Scot Jenkins via TUHS
2024-06-08 10:19 ` [TUHS] POSIX ed(1)'s exit status. (Was: diving into vi...) Ralph Corderoy
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=CALMnNGhBsw4t3Bar5JVd_UWjhO2kNMGGrKchMRS8CmFpuhd1Hw@mail.gmail.com \
--to=akosela@andykosela.com \
--cc=tuhs@tuhs.org \
--cc=will.senn@gmail.com \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).