all messages for Emacs-related lists mirrored at yhetil.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 16:40:57 -0500 (CDT)	[thread overview]
Message-ID: <200209232140.QAA09746@eel.dms.auburn.edu> (raw)
In-Reply-To: <200209230244.VAA07692@eel.dms.auburn.edu> (message from Luc Teirlinck on Sun, 22 Sep 2002 21:44:30 -0500 (CDT))


   The output of C-h v end-of-line contains the following line:

   if N is nil or 1, and point starts at a field boundary, point does not
   move.

   This is not quite accurate: there is an exception.  Point does not
   move *unless* the previous character has a non-nil rear-nonsticky
   text-property *and* a text-property field eq to boundary.  Then point
   *does* move over the field.  Comint and its derived modes rely heavily
   on this exception.

Actually, although the description of the situation is correct, my
interpretation of it was, I believe wrong.

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.

Sincerely,

Luc.

  parent reply	other threads:[~2002-09-23 21:40 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 [this message]
2002-09-23 21:59   ` Luc Teirlinck
2002-09-23 22:31   ` Luc Teirlinck
2002-09-23 23:55   ` Luc Teirlinck
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=200209232140.QAA09746@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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.