From: Miles Bader <miles@lsi.nec.co.jp>
Cc: emacs-devel@gnu.org
Subject: Re: buff-menu.el changes
Date: 17 Dec 2002 10:30:37 +0900 [thread overview]
Message-ID: <buod6o1ctz6.fsf@mcspd15.ucom.lsi.nec.co.jp> (raw)
In-Reply-To: <20021217000015.50ec6208.occitan@esperanto.org>
Daniel Pfeiffer <occitan@esperanto.org> writes:
> Being able to move over intangible text charwise but not linewise sounds
> counterintuitive and would seem a 21.3 bug.
Almost certainly; the `line-move' function is chock full of special
code to deal with intangible characters, which in my experience breaks
often, and never _really_ works correctly. I don't really understand
the it that well, but I think the problem often involves hidden
newline characters.
If anyone's interested, here's a simple test-case that illustrates the
problem:
(with-current-buffer (get-buffer-create "*test*")
(insert "1: hello\n")
(insert (propertize "2: cruel\n" 'invisible t 'intangible t))
(insert "3: world\n")
(insert "4:\n"))
After evaluating that, go to the *test* buffer, and move around using
C-n & C-p. I can see the following bugs:
(1) If the cursor is in the first column, you can't move from line
"3:" to line "4:" using C-n (but C-p works all the way from the
end of the buffer to the beginning).
(2) If the cursor is in a different column, C-n seems to work
correctly on all lines, but C-p won't move from line "3:" to
line "1:" (it seems to work on all other line though).
-Miles
--
Somebody has to do something, and it's just incredibly pathetic that it
has to be us. -- Jerry Garcia
next prev parent reply other threads:[~2002-12-17 1:30 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-12-16 20:04 buff-menu.el changes Robert J. Chassell
2002-12-16 21:05 ` Juanma Barranquero
2002-12-16 23:00 ` Daniel Pfeiffer
2002-12-17 1:30 ` Miles Bader [this message]
2002-12-17 17:00 ` intangible characters bugs [was Re: buff-menu.el changes] Robert J. Chassell
2002-12-18 20:40 ` buff-menu.el changes Robert J. Chassell
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=buod6o1ctz6.fsf@mcspd15.ucom.lsi.nec.co.jp \
--to=miles@lsi.nec.co.jp \
--cc=emacs-devel@gnu.org \
--cc=miles@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).