unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Lennart Borgman <lennart.borgman@gmail.com>
To: Elena <egarrulo@gmail.com>
Cc: help-gnu-emacs@gnu.org
Subject: Re: Viper: replacing text?
Date: Thu, 3 Sep 2009 23:53:35 +0200	[thread overview]
Message-ID: <e01d8a50909031453n14cc7dfaw4c4f74d65b588037@mail.gmail.com> (raw)
In-Reply-To: <0ea65763-4e18-4150-8e49-88de271c7c12@g19g2000yqo.googlegroups.com>

On Thu, Sep 3, 2009 at 9:38 PM, Elena<egarrulo@gmail.com> wrote:
> On 3 Set, 18:38, Sean Sieger
>> But I guess where I'm coming from is the `GNU/Emacs v Vi' thing (I've
>> used Vi, and it seems like a cool text editor) and personally preferring
>> GNU/Emacs and then wondering why on Earth I would then want it to behave
>> like Vi.
>>
>> Essentially.
>
> I understand.
>
> IMO, comparing Vi and Emacs does not make sense. Vi is an editor,
> Emacs is an environment. You can just compare Vi to the default
> editing program run by Emacs. Emacs can also run a Vi-like editor
> (Viper), if you like - I like so ;-)
>
> Indeed Emacs allows you to run two editors at once! (Viper and the
> default one)
>
> BTW, I'm waiting for a pure Viper solution I'm sure Lennart is still
> keeping for him ;-)

I should keep my mouth shut ... ;-)

Now, since I did not this time, let us do a quick comparision with
Sean's suggestion, translating from Emacs default key sequences to
Viper dito:

   M-d
   C-f
   M-d
   C-u 2 C-y

You can do this in a very similar way in Viper (but I do not know if
it is actually worth the effort using and remembering "2P):

   dw (or de, dE, dW, db, dB)
   h
   dw
   "2P

I count it to 11 keyboard hits in Emacs and 8 in Viper... - though I
hardly dare to tell this ... ;-)

Someone may say I am wrong since " and P requires shift on most
keyboards so it is really 10 in Viper...

The real advantage with the Viper keys is in my opinion perhaps that
you use the keyboard keys you reach very fast, ie normal letters. At
least for me reaching Control and Meta is a bit slower.

However in the beginning getting used to the vi modal editing is a bit
hard. (There is a little Viper interactive tutorial, but unfortunately
RMS did not want it to be shipped with Emacs, no idea why now, I have
forgotten. I ship it with nXhtml instead.)

Note that you still have access to most of the Emacs key bindings in
Viper. They are still very useful for more complicated things, but
most Viper users probably never use M-d, C-f etc.




  reply	other threads:[~2009-09-03 21:53 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 14:11 Viper: replacing text? Elena
2009-09-03 15:05 ` Lennart Borgman
     [not found] ` <mailman.5945.1251990364.2239.help-gnu-emacs@gnu.org>
2009-09-03 15:21   ` Elena
2009-09-03 15:40 ` Sean Sieger
2009-09-03 16:13   ` Lennart Borgman
2009-09-03 16:38     ` Sean Sieger
     [not found]     ` <mailman.5955.1251995918.2239.help-gnu-emacs@gnu.org>
2009-09-03 19:38       ` Elena
2009-09-03 21:53         ` Lennart Borgman [this message]
2009-09-04  1:19           ` Sean Sieger
     [not found]           ` <mailman.5983.1252027190.2239.help-gnu-emacs@gnu.org>
2009-09-04  7:58             ` Anselm Helbig
2009-09-04 10:41               ` Sean Sieger
     [not found]         ` <mailman.5974.1252014851.2239.help-gnu-emacs@gnu.org>
2009-09-03 22:51           ` Elena
2009-09-04  8:02             ` Anselm Helbig
2009-09-04  8:31               ` Elena
     [not found] ` <mailman.5946.1251992506.2239.help-gnu-emacs@gnu.org>
2009-09-03 15:58   ` Elena
2009-09-03 17:00     ` Sean Sieger
2009-09-03 17:01     ` Sean Sieger

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

  List information: https://www.gnu.org/software/emacs/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=e01d8a50909031453n14cc7dfaw4c4f74d65b588037@mail.gmail.com \
    --to=lennart.borgman@gmail.com \
    --cc=egarrulo@gmail.com \
    --cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).