From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Cc: Tyler Spivey <tspivey@pcdesk.net>
Subject: Re: Problem with gnus-article-hide-citation
Date: Mon, 29 Sep 2008 11:25:12 +0200 [thread overview]
Message-ID: <kziqsf9udj.fsf@kafka.physik3.gwdg.de> (raw)
In-Reply-To: <b4m3ajjlukc.fsf@jpl.org> (Katsumi Yamaoka's message of "Mon, 29 Sep 2008 08:28:03 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
> I doubted the behavior of C-a (i.e. move-beginning-of-line) is
> really useful. It moves the point to the next visible field,
> but shouldn't it be the end of the previous visible field (or
> the beginning of the buffer)? Anyway, how about trying the
> following for a while? It is just what Emacs 21 does:
>
> (global-set-key "\C-a" 'beginning-of-line)
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. 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:25 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 [this message]
2008-09-29 9:45 ` Katsumi Yamaoka
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=kziqsf9udj.fsf@kafka.physik3.gwdg.de \
--to=deng@randomsample.de \
--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).