From: Richard Stallman <rms@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: Mon, 18 Mar 2002 13:07:31 -0700 (MST) [thread overview]
Message-ID: <200203182007.g2IK7VK08811@wijiji.santafe.edu> (raw)
In-Reply-To: <buou1rey4yg.fsf@mcspd15.ucom.lsi.nec.co.jp> (message from Miles Bader on 18 Mar 2002 11:39:35 +0900)
The reason it does this is because the minibuffer input field is at the
end of the buffer, and can have a size of zero. Thus any inserted
characters will have nil values for their properties, including the
`field' property. Also, it's important that the field code recognize
that there's an empty field there, so that commands such as C-a don't
act wierdly when nothing's been typed into the minibuffer.
However, I think this can be handled by making the minibuffer input use
an overlay for the input field, instead of relying on the nil-properties
inserted at the end of the buffer.
That part bothers me. Can we assign a coherent meaning to a field
property on an empty overlay?
_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://mail.gnu.org/mailman/listinfo/emacs-devel
next prev parent reply other threads:[~2002-03-18 20: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
2002-03-19 9:24 ` Miles Bader
2002-03-19 8:44 ` Richard Stallman
2002-03-18 20:07 ` Richard Stallman [this message]
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=200203182007.g2IK7VK08811@wijiji.santafe.edu \
--to=rms@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).