Gnus development mailing list
 help / color / mirror / Atom feed
From: Samuel Padgett <spadgett1@nc.rr.com>
Cc: Daniel Pittman <daniel@rimspace.net>, ding@gnus.org
Subject: Re: Q: Use external editor for Gnus?
Date: Tue, 23 Oct 2001 09:53:51 -0400	[thread overview]
Message-ID: <87hesqea34.fsf@harpo.homeip.net> (raw)
In-Reply-To: <vafpu7elqpq.fsf@INBOX.auto.gnus.tok.lucy.cs.uni-dortmund.de> (Kai.Grossjohann@CS.Uni-Dortmund.DE's message of "Tue, 23 Oct 2001 10:12:49 +0200")

Kai.Grossjohann@CS.Uni-Dortmund.DE (Kai Großjohann) writes:

> Now, if they were addicted to vi keybindings, we could just tell them
> to use viper.  But with vim keybindings?

FWIW, Vim has a lot of stuff that Viper doesn't.  Many key bindings
are, of course, the same: the "basic" Vi key bindings.  All of the
"window" commands are different, and Vim has a lot of ex commands that
just aren't defined in Viper.  Also, commands that operate on regions
are different.  But I think most of this wouldn't matter when just
composing mail.

One piece of advice, though: if they use Viper at a lower "expert
level", make sure they choose one high enough that ":q", ":wq", "Z Z",
and friends don't quit the editor.  In Mutt/Vim and slrn/Vim, these
are the keys you typically use to send the message.  (Actually, I
don't think it's possible to make :q or :wq to send the message
without hacking Viper internals, but it's easy to make "Z Z" do it.
There's even an example for this in the Viper manual.)

HTH,
Sam



  parent reply	other threads:[~2001-10-23 13:53 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2001-10-22 21:07 Kai Großjohann
2001-10-23  2:44 ` Daniel Pittman
2001-10-23  8:12   ` Kai Großjohann
2001-10-23  8:52     ` Daniel Pittman
2001-10-27 22:49       ` Florian Weimer
2001-10-28  9:37         ` Daniel Pittman
2001-10-23 13:53     ` Samuel Padgett [this message]
2001-10-23 15:03       ` Kai Großjohann
2001-10-24  2:30         ` Samuel Padgett

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=87hesqea34.fsf@harpo.homeip.net \
    --to=spadgett1@nc.rr.com \
    --cc=daniel@rimspace.net \
    --cc=ding@gnus.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).