Gnus development mailing list
 help / color / mirror / Atom feed
From: nyc4bos@aol.com
To: ding@gnus.org
Subject: Summary buffer weirdness with gnus-summary-limit-to-unseen
Date: Tue, 07 Dec 2010 19:04:22 -0500	[thread overview]
Message-ID: <46fwu9uo3d.fsf@aol.com> (raw)

Hi,

I'm seeing some weirdness when using `gnus-summary-limit-to-unseen'

To reproduce:

1. Startup Gnus
2. Hit SPC `gnus-group-read-group' on the group gmane.emacs.gnus.general
3. Hit <return> to select all articles
4. When the *Summary* buffer appears, hit /. `gnus-summary-limit-to-unseen'
5. Hit SPC on the article with the subject:

   Re: SPAM in spam group is processed into that exact same group

 11k│R. │Tassilo Horn
   (Message-ID: <201012051913.36404.tassilo@member.fsf.org>)

6. Hit TAB `gnus-summary-widget-forward' until you get to:

    <87tyk8x03w.fsf@lifelogs.com>

7. Hit <return> `widget-button-press'

You will then go to the article Tassilo referenced, but the *Summary*
buffer will now show the cursor on the first (unread) article, which is,
in this case:

4.1k│R. │John Sullivan          ║ ┏●  stack overflow in regexp matcher

Additionally, this article now has a "R" (read) mark even though it
was not selected.

It appears that almost everything works expected if you don't
press /. `gnus-summary-limit-to-unseen', first.

BTW, how do you go back to Tassilo's article after `widget-button-press'
and calling `gnus-button-handle-news' news:87tyk8x03w.fsf@lifelogs.com?





             reply	other threads:[~2010-12-08  0:04 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-12-08  0:04 nyc4bos [this message]
2010-12-16 17:22 ` Lars Magne Ingebrigtsen

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=46fwu9uo3d.fsf@aol.com \
    --to=nyc4bos@aol.com \
    --cc=ding@gnus.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.
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).