unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Luc Teirlinck <teirllm@dms.auburn.edu>
Cc: emacs-devel@gnu.org
Subject: Re: bug in ielm: patch.  Related problem with end-of-line.
Date: Mon, 23 Sep 2002 18:55:16 -0500 (CDT)	[thread overview]
Message-ID: <200209232355.SAA09873@eel.dms.auburn.edu> (raw)
In-Reply-To: <200209232140.QAA09746@eel.dms.auburn.edu> (message from Luc Teirlinck on Mon, 23 Sep 2002 16:40:57 -0500 (CDT))

From my previous message:

   If point is at the beginning of a buffer, or after a character with a
   rear-nonsticky field property, different from the following
   character's field property, then I believe C-e should move point over
   the following field, regardless of whether the previous character's
   field property is `boundary'.  I checked that this actually was the
   behavior in emacs-21.2.90.  The problems I described do not occur in
   21.2.90.  So maybe it might be good to revert to the 21.2.90 behavior.

Actually my description of the emacs-21.2.90 behavior here and in some
subsequent messages was wrong.  The emacs-21.2.90 behavior of C-e with
respect to text-properties actually seems identical to the
emacs-21.3.50 behavior.  I was confused by the fact that in
emacs-21.3.50 comint used overlays instead of text properties.  That
seems to be why the described problem did not occur in 21.2.90, at
least not in comint buffers.

Sorry for the confusion.

Sincerely,

Luc.

  parent reply	other threads:[~2002-09-23 23:55 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2002-09-23  2:44 bug in ielm: patch. Related problem with end-of-line Luc Teirlinck
2002-09-23  3:50 ` Luc Teirlinck
2002-09-23 21:40 ` Luc Teirlinck
2002-09-23 21:59   ` Luc Teirlinck
2002-09-23 22:31   ` Luc Teirlinck
2002-09-23 23:55   ` Luc Teirlinck [this message]
2002-09-24  0:16     ` Luc Teirlinck

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=200209232355.SAA09873@eel.dms.auburn.edu \
    --to=teirllm@dms.auburn.edu \
    --cc=emacs-devel@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).