From: Richard Stallman <rms@gnu.org>
Subject: Moving out of invisible text
Date: Sat, 11 Mar 2006 10:46:49 -0500 [thread overview]
Message-ID: <E1FI6Ir-0001o4-HT@fencepost.gnu.org> (raw)
With the bug fix that was recently made, is this proposed change
in lispref/display.texi correct?
*** display.texi 21 Feb 2006 08:42:07 -0000 1.203
--- display.texi 11 Mar 2006 15:16:23 -0000
***************
*** 800,814 ****
@code{line-move-ignore-invisible} is non-@code{nil} (the default), but
only because they are explicitly programmed to do so.
! However, if a command ends with point inside or immediately after
invisible text, the main editing loop moves point further forward or
further backward (in the same direction that the command already moved
it) until that condition is no longer true. Thus, if the command
moved point back into an invisible range, Emacs moves point back to
! the beginning of that range, following the previous visible character.
! If the command moved point forward into an invisible range, Emacs
! moves point forward past the first visible character that follows the
! invisible text.
Incremental search can make invisible overlays visible temporarily
and/or permanently when a match includes invisible text. To enable
--- 800,814 ----
@code{line-move-ignore-invisible} is non-@code{nil} (the default), but
only because they are explicitly programmed to do so.
! However, if a command ends with point inside or immediately before
invisible text, the main editing loop moves point further forward or
further backward (in the same direction that the command already moved
it) until that condition is no longer true. Thus, if the command
moved point back into an invisible range, Emacs moves point back to
! the beginning of that range, and then back one more character. If the
! command moved point forward into an invisible range, Emacs moves point
! forward up to the first visible character that follows the invisible
! text.
Incremental search can make invisible overlays visible temporarily
and/or permanently when a match includes invisible text. To enable
reply other threads:[~2006-03-11 15:46 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=E1FI6Ir-0001o4-HT@fencepost.gnu.org \
--to=rms@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.