From: Bill Lear <rael@zopyra.com>
To: bug-gnu-emacs@gnu.org
Subject: Why I may not use emacs any more for coding
Date: Thu, 6 Mar 2008 20:20:33 -0600 [thread overview]
Message-ID: <18384.42609.332493.397051@lisa.zopyra.com> (raw)
Perhaps it's a new world, more full of greed and attendant pressures
to perform immediately, that pushes me to prefer things with more
responsiveness, but I have found myself drifting away from emacs
towards vim, despite my strong sympathy for Mr. Stallman's baby-beast.
The cause of this is quite simple, and I am hoping that someone
here can help me.
I prefer vi editing within emacs (via viper-mode) as I find it
efficient and comfortable, and this has worked wonderfully, EXCEPT
when I need to use this combination within an xterm, as is often the
case for me.
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.
I have searched in vain, in a sporadic, but concentrated efforts, over
the past several years to find an answer to this conundrum ---
searching everything from X windows, emacs, vi/vim, viper-mode,
and other forums for an answer, to no avail.
Could anyone here please help me figure out how to do away with this
ridiculous delay? If I could recover this responsiveness, I would
surely revert to the side of good and purity, and turn away from the
darkness.
Thank you in advance for your help.
Bill
next reply other threads:[~2008-03-07 2:20 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-03-07 2:20 Bill Lear [this message]
2008-03-07 11:00 ` Why I may not use emacs any more for coding Johan Bockgård
2008-03-07 13:04 ` Bill Lear
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
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=18384.42609.332493.397051@lisa.zopyra.com \
--to=rael@zopyra.com \
--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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).