unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Miles Bader <miles@gnu.org>
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 09:02:27 +0900	[thread overview]
Message-ID: <87y9gp8lws.fsf@tc-1-100.kawasaki.gol.ne.jp> (raw)
In-Reply-To: <5x8z8pak2s.fsf@kfs2.cua.dk>

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.

> I said 'indicates' -- as the major example of using this feature doesn't
> work, and need to be reworked using more machinery (rather than less).

Of course it works.  The reason why it's a bit wierd is because the
input field is at the of the buffer, and _everything_ involving
text properties works a bit oddly at the end of the buffer.  [your
proposed `solution' would have exactly the same problem!]

> Ok, but it sometimes does make sense to navigate inside the prompt.
> C-e -> goto end of prompt (= start of input), another C-e -> go to
> end of input.  Isn't that how it's working now?

Yes, but people apparently don't like it (I don't really care).  They
want C-e to go to the `end of something', not `the beginning'.  Even
though the `background' is a field too by definition, people think of
the input field as being distinguished from the background, and I
suppose emacs ought to respect that.

> I thought you were proposing to change, end-of-line and other
> commands to behave differently if point is "inside" a field.

I'm proposing changing the way the field-restriction functions work
(which are called by anyone that cares about a field) to not act like
it's a field when the field property is nil.

> I referred to that as "messy" (compared to doing it through command
> remapping).

I suspect trying to do it through command remapping would actually be a
lot messier -- because you're only changing things at a surface level,
you have a lot more special cases to worry about.

[and in any case, the current mechanism (1) exists, and (2) works quite well]

-Miles
-- 
I'd rather be consing.

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel


  reply	other threads:[~2002-03-19  0:02 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 [this message]
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

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=87y9gp8lws.fsf@tc-1-100.kawasaki.gol.ne.jp \
    --to=miles@gnu.org \
    --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).