From: Miles Bader <miles@lsi.nec.co.jp>
Cc: rms@gnu.org, emacs-pretest-bug@gnu.org, emacs-devel@gnu.org
Subject: Re: [ortmann@isl.net: asymmetries and contradictions in shell navigation using C-a and C-e on a prompt line]
Date: 20 Mar 2002 15:38:03 +0900 [thread overview]
Message-ID: <buok7s73fsk.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <Pine.SUN.3.91.1020320082838.25160J-100000@is>
Eli Zaretskii <eliz@is.elta.co.il> writes:
> > However, I don't really care about the problem (C-e/C-k acting
> > `unintuitively' inside prompts) very much, so I'm quite content to
> > not fix it.
>
> If we decide that this won't be fixed, at least for a while, we could
> have an entry in PROBLEMS that suggests work-arounds, or at least
> acknowledges the existence of the problem.
I suspect most people figure out the `workaround' (hit the key twice
instead of once) by themselves pretty quickly.
-Miles
--
`...the Soviet Union was sliding in to an economic collapse so comprehensive
that in the end its factories produced not goods but bads: finished products
less valuable than the raw materials they were made from.' [The Economist]
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
prev parent reply other threads:[~2002-03-20 6:38 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <200201210941.g0L9f9s14343@aztec.santafe.edu>
2002-03-18 2:39 ` [ortmann@isl.net: asymmetries and contradictions in shell navigation using C-a and C-e on a prompt line] Miles Bader
2002-03-18 15:17 ` Kim F. Storm
2002-03-18 15:39 ` Miles Bader
2002-03-18 16:59 ` Kim F. Storm
2002-03-19 0:02 ` Miles Bader
2002-03-19 9:07 ` Kim F. Storm
2002-03-19 9:24 ` Miles Bader
2002-03-19 8:44 ` Richard Stallman
2002-03-18 20:07 ` Richard Stallman
2002-03-19 0:18 ` Miles Bader
2002-03-20 5:11 ` Richard Stallman
2002-03-20 5:41 ` Miles Bader
2002-03-20 6:30 ` Eli Zaretskii
2002-03-20 6:38 ` Miles Bader [this message]
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=buok7s73fsk.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@gnu.org \
--cc=miles@gnu.org \
--cc=rms@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).