From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Cc: Tyler Spivey <tspivey@pcdesk.net>
Subject: Re: Problem with gnus-article-hide-citation
Date: Mon, 29 Sep 2008 18:45:44 +0900 [thread overview]
Message-ID: <b4mk5cvuvxz.fsf@jpl.org> (raw)
In-Reply-To: <kziqsf9udj.fsf@kafka.physik3.gwdg.de>
>>>>> David Engster wrote:
> The problem is that the hidden text practically shadows the first
> character of the visible one. You may try this with the following test
> code:
> (save-excursion
> (set-buffer (get-buffer-create "invtest"))
> (erase-buffer)
> (insert "\naaaaa\nbbbbb\n")
> (goto-char (point-min))
> (forward-line 1)
> (set-text-properties (point) (1+ (point-at-eol)) '(invisible t intangible t)))
> Now switch to the buffer "invtest", and put the cursor on the first
> "b". Doing C-x = here will show the hidden "a" on position 2. If you go
> one step to the right, C-x = will (correctly) show the second "b" at
> position 9.
Emacs 22.1 behaves similarly, but in Emacs 21.4, the cursor doesn't
move and C-x = shows the first "b" at position 8. One more step to
the right, the cursor moves to the second "b". It seems to be a bug
that has been introduced in Emacs 22.
> In fact, it seems you cannot really access the first "b" at
> position 8 through cursor movements. Therefore, EmacsSpeak would not
> only have to ignore invisible text, but skip it until it reaches the
> first visible character. This seems rather odd to me, and I also didn't
> expect that behavior after reading the section on invisible text in the
> ELisp reference.
> -David
next prev parent reply other threads:[~2008-09-29 9:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87y71eeav9.fsf@pcdesk.net>
2008-09-27 16:32 ` David Engster
2008-09-28 23:28 ` Katsumi Yamaoka
2008-09-29 9:25 ` David Engster
2008-09-29 9:45 ` Katsumi Yamaoka [this message]
2008-09-29 10:35 ` David Engster
2008-10-04 13:51 ` David Engster
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=b4mk5cvuvxz.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.org \
--cc=tspivey@pcdesk.net \
/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.
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 NNTP newsgroup(s).