From: "積丹尼 Dan Jacobson" <jidanni@jidanni.org>
To: 34473@debbugs.gnu.org
Subject: bug#34473: Discuss "old/ancient" articles more
Date: Thu, 14 Feb 2019 10:05:34 +0800 [thread overview]
Message-ID: <875ztn3z0x.fsf@jidanni.org> (raw)
In (info "(gnus) Read Articles") one reads about
‘O’
Articles that were marked as read in previous sessions and are now
“old” (‘gnus-ancient-mark’).
Well you need to say more:
* How do discover if one has "old/ancient" articles.
(Say tip: Use 99999 RET to enter a (e.g., nnml) group, instead of just RET.)
* What "old/ancient" articles are.
* How to prevent them from accruing.
Gnus v5.13
GNU Emacs 26.1 (build 2, x86_64-pc-linux-gnu, GTK+ Version 3.24.4)
of 2019-02-03, modified by Debian
next reply other threads:[~2019-02-14 2:05 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-02-14 2:05 積丹尼 Dan Jacobson [this message]
2019-07-09 17:07 ` bug#34473: Discuss "old/ancient" articles more Lars Ingebrigtsen
2019-07-11 0:43 ` 積丹尼 Dan Jacobson
2019-07-11 14:07 ` Lars 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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=875ztn3z0x.fsf@jidanni.org \
--to=jidanni@jidanni.org \
--cc=34473@debbugs.gnu.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).