From: "Clemens Schüller" <cs.mlists+gnus@mailbox.org>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: ding@gnus.org
Subject: Re: Going to next unseen article?
Date: Mon, 08 Apr 2019 17:23:02 +0200 [thread overview]
Message-ID: <m2pnpw5xnt.warhorse@cmschueller.my-fqdn.de> (raw)
In-Reply-To: <87a7h1z75l.fsf@web.de> (Michael Heerdegen's message of "Mon, 08 Apr 2019 02:12:54 +0200")
Hello!
On 08. Apr. 2019, Michael Heerdegen wrote:
> Hi,
>
> seems there is no summary command to go to the next unseen article. Or
> did I miss it, or can this be done in some way I missed? The only thing I
> found is / . (`gnus-summary-limit-to-unseen').
>
> Something like `gnus-summary-next-unseen-article' would be useful for
> people like me who tend to have a lot of older unread articles but only
> want to check the unseen ones. Seems gnus-sum.el is not really prepared
> for the task however.
>
> Opinions?
Maybe this could be the right solution for you :-)
--8<---------------cut here---------------start------------->8---
n runs the command gnus-summary-next-unread-article (found in
gnus-summary-mode-map), which is an interactive compiled Lisp function
in ‘gnus-sum.el’.
It is bound to n, G n, <menu-bar> <Gnus> <Move> <Next unread article>.
(gnus-summary-next-unread-article)
Select unread article after current one.
--8<---------------cut here---------------end--------------->8---
--
Best Regards, Clemens Schüller
next prev parent reply other threads:[~2019-04-08 15:23 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 [this message]
2019-04-08 16:04 ` Eric S Fraga
2019-04-10 0:57 ` Michael Heerdegen
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=m2pnpw5xnt.warhorse@cmschueller.my-fqdn.de \
--to=cs.mlists+gnus@mailbox.org \
--cc=cs.mlists@mailbox.org \
--cc=ding@gnus.org \
--cc=michael_heerdegen@web.de \
/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).