From: Michael Heerdegen <michael_heerdegen@web.de>
To: Eric S Fraga <e.fraga@ucl.ac.uk>
Cc: ding@gnus.org
Subject: Re: Going to next unseen article?
Date: Wed, 10 Apr 2019 02:57:32 +0200 [thread overview]
Message-ID: <87o95en0cj.fsf@web.de> (raw)
In-Reply-To: <87k1g47aam.fsf@ucl.ac.uk> (Eric S. Fraga's message of "Mon, 08 Apr 2019 17:04:49 +0100")
Eric S Fraga <e.fraga@ucl.ac.uk> writes:
> Unfortunately, no; the OP does not want the next unread but the next
> unseen instead (ones with . in the summary line).
Yes, exactly.
Ok, I filed a report to "The Gnus Bugfixing Girls + Boys", it's now
Bug#35213. How many girls are among these, btw?
Michael.
prev parent reply other threads:[~2019-04-10 0:57 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-04-08 0:12 Michael Heerdegen
2019-04-08 15:23 ` Clemens Schüller
2019-04-08 16:04 ` Eric S Fraga
2019-04-10 0:57 ` Michael Heerdegen [this message]
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=87o95en0cj.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=ding@gnus.org \
--cc=e.fraga@ucl.ac.uk \
/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).