From: storm@cua.dk (Kim F. Storm)
Cc: 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: 19 Mar 2002 10:07:25 +0100 [thread overview]
Message-ID: <5x1yehdiya.fsf@kfs2.cua.dk> (raw)
In-Reply-To: <87y9gp8lws.fsf@tc-1-100.kawasaki.gol.ne.jp>
Miles Bader <miles@gnu.org> writes:
> no-spam@cua.dk (Kim F. Storm) writes:
> > I don't understand. How does emacs know when it's currently in an important
> > case...
>
> What are you talking about? I mean _I've_ thought about how things
> work, and considered the important cases when the current mechanism is
> confusing in this way, and decided that this is a good solution.
Ok, but why do you ask people what they think and whether there are
other ways to fix this?
I took the time to think about this, and told you what I thought -
and I'm sorry that I didn't understand what you were proposing to
change.
--
Kim F. Storm <storm@cua.dk> http://www.cua.dk
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-19 9:07 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 [this message]
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
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=5x1yehdiya.fsf@kfs2.cua.dk \
--to=storm@cua.dk \
--cc=emacs-devel@gnu.org \
--cc=emacs-pretest-bug@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).