From: "Thomas Paulsen" <thomas.paulsen@firemail.de>
To: <g.branden.robinson@gmail.com>
Cc: tuhs@tuhs.org
Subject: Re: [TUHS] block operations in editors, was My EuroBSDcon talk
Date: Tue, 17 Sep 2019 13:34:05 +0200 [thread overview]
Message-ID: <c5b6170c342996b6161a24a9c95a68b3@firemail.de> (raw)
---------------------------------
>
> Though the vi clone with the best name was, indisputably, elvis.
>
unfortunately unmaintained.
elvis has a smaller memory footprint, and a more pleasant (nroff later html) based help support than vim. There are no plugin, vimscript feature sas well as no python/perl support. I'm interested in a vi with syntax coloring and help support, however I don't need scripting features. Therefore I hope someone will take over maintenance, as I'm too old for tha
next reply other threads:[~2019-09-17 11:34 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-17 11:34 Thomas Paulsen [this message]
-- strict thread matches above, loose matches on Subject: below --
2019-09-17 17:31 Doug McIlroy
2019-09-18 4:47 ` Steve Johnson
2019-09-18 4:52 ` Jon Steinhart
2019-09-17 15:36 Noel Chiappa
2019-09-17 0:20 Doug McIlroy
2019-09-17 0:42 ` G. Branden Robinson
2019-09-17 2:02 ` George Michaelson
2019-09-17 11:01 ` Thomas Paulsen
2019-09-17 1:25 ` Bakul Shah
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=c5b6170c342996b6161a24a9c95a68b3@firemail.de \
--to=thomas.paulsen@firemail.de \
--cc=g.branden.robinson@gmail.com \
--cc=tuhs@tuhs.org \
/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).