all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Bill Lear <rael@zopyra.com>
To: bojohan+news@dd.chalmers.se (Johan Bockgård)
Cc: bug-gnu-emacs@gnu.org
Subject: Re: Why I may not use emacs any more for coding
Date: Fri, 7 Mar 2008 07:04:21 -0600	[thread overview]
Message-ID: <18385.15701.931636.175130@lisa.zopyra.com> (raw)
In-Reply-To: <yoijbq5q4x4d.fsf@remote2.student.chalmers.se>

On Friday, March 7, 2008 at 12:00:34 (+0100) Johan =?utf-8?Q?Bockg=C3=A5rd?= writes:
>Bill Lear <rael@zopyra.com> writes:
>
>> When using emacs inside an xterm (emacs -nw) with viper-mode, I find
>> an intolerable delay in the transition between editing and navigating
>> modes (reminder: this is effected by pressing the ESC key while in
>> editing mode).  In vim/vi or in emacs outside of an xterm, I can
>> effect this transition with such speed that my fingers need not pause
>> after the ESC key is pressed before I begin my input of navigation
>> keystrokes, whereas under an xterm if attempt this transition, it
>> seems (based on observation only) that this takes AT LEAST 500
>> milliseconds --- easily enough time to enter a half-dozen navigation
>> commands (up two lines and over four words: 'kkwwww').  Over the
>> course of a typical edit cycle, this interruption has become more and
>> more intolerable to me.
>
>Investigate `viper-ESC-keyseq-timeout' (and maybe
>`viper-translate-all-ESC-keysequences' and `viper-no-multiple-ESC').

This looks like what I need.  Many thanks for the quick reply.


Bill




  reply	other threads:[~2008-03-07 13:04 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-03-07  2:20 Why I may not use emacs any more for coding Bill Lear
2008-03-07 11:00 ` Johan Bockgård
2008-03-07 13:04   ` Bill Lear [this message]
2008-03-08  6:28     ` Richard Stallman

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=18385.15701.931636.175130@lisa.zopyra.com \
    --to=rael@zopyra.com \
    --cc=bojohan+news@dd.chalmers.se \
    --cc=bug-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.
Code repositories for project(s) associated with this external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.