Gnus development mailing list
 help / color / mirror / Atom feed
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: Sat, 27 Sep 2008 18:32:20 +0200	[thread overview]
Message-ID: <87r675r1m3.fsf@engster.org> (raw)
In-Reply-To: <87y71eeav9.fsf@pcdesk.net> (Tyler Spivey's message of "Fri, 26 Sep 2008 16:38:34 -0700")

[Followup from gnus.bug]

Tyler Spivey <tspivey@pcdesk.net> writes:
> I'll try to describe this bug as best I can, so hopefully it can get
> fixed. When I press WWc on a message, then start cursoring around the
> article buffer, the > characters are still in it. They aren't visible
> on the screen, but I am blind and use an emacs speech package which
> picks them up. To reproduce this, press WWc on a message, then put
> point on the first character of any remaining text that wasn't hidden
> (below the buttons). press C-a C-b, the cursor should be on a blank
> line, but note that if you press C-x = the current character is a >.
> Also, if you hit C-a on that line, it'll jump you to the next line.

I can confirm this behavior. I'm not sure why this is happening and if
this is actually a bug in Gnus or in Emacs. I always thought that the
user commands for cursor navigation would skip over hidden text, but in
the first column in the line after the button, the point position is
indeed on the beginning of the hidden citation, usually containing a
">".

I tried putting the hidden text directly after the button (i.e. in the
same line). It is still accessible, but it would be at a line ending and
not at the beginning of the next line, which I guess would at least
solve the above problem?

Other suggestions?

-David



       reply	other threads:[~2008-09-27 16:32 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 [this message]
2008-09-28 23:28   ` Katsumi Yamaoka
2008-09-29  9:25     ` David Engster
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=87r675r1m3.fsf@engster.org \
    --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).