Gnus development mailing list
 help / color / mirror / Atom feed
From: lee <lee@yun.yagibdah.de>
To: ding@gnus.org
Subject: Re: Gnus Questions #1: Article Expiry
Date: Wed, 06 Jul 2011 21:55:15 +0200	[thread overview]
Message-ID: <87r563xjz0.fsf@yun.yagibdah.de> (raw)
In-Reply-To: <m2vcvfxnyt.fsf@pluto.luannocracy.com> (Dave Abrahams's message of "Wed, 06 Jul 2011 14:28:58 -0400")

Dave Abrahams <dave@boostpro.com> writes:

>> I mean, there is no mark for "expired articles" (i.e. deleted
>> articles) as far as I know.  Just "expirable articles".
>
> I agree and am inclined to think we need to s/expired/expirable/ in
> the referenced info node.  I'll put that in my patch.

,---- [ info (gnus) Read Articles ]
| `r'
|      These are articles that the user has marked as read with the `d'
|      command manually, more or less (`gnus-del-mark').
`----

,---- [ info (gnus) Setting Marks ]
| `M d'
| `d'
|      Mark the current article as read
|      (`gnus-summary-mark-as-read-forward').
| 
| `D'
|      Mark the current article as read and move point to the previous
|      line (`gnus-summary-mark-as-read-backward').
`----

The `gnus-del-mark' still exists in gnus-score.el, gnus.el and
gnus-sum.el.

> [...]
>>>     ,----
>>>     | To avoid having articles marked as read marked as
>>>     | expirable automatically, you can put something like the following in
>>>     | your `~/.gnus.el' file:
>>>     | 
>>>     |      (remove-hook 'gnus-mark-article-hook
>>>     |                   'gnus-summary-mark-read-and-unread-as-read)
>>>     |      (add-hook 'gnus-mark-article-hook 'gnus-summary-mark-unread-as-read)
>>>     | 
>>>     `----
>>
>> Yes, that seems rather excessive.
>
> Any objections if I remove that passage in my patch?

Yes :)  It's nice to have examples like this in the documentation.  How
else are users supposed to figure out what they could do?  See also the
chapter "3.3.2 Choosing Variables" (which also mentions `gnus-del-mark',
btw.).



  reply	other threads:[~2011-07-06 19:55 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-07-03 23:30 Dave Abrahams
2011-07-04 14:29 ` lee
2011-07-05  0:50   ` Dave Abrahams
2011-07-05 21:51     ` lee
2011-07-05 22:46       ` lee
2011-07-06 18:32         ` Dave Abrahams
2011-07-06 19:24           ` lee
2011-07-05 20:44 ` Lars Magne Ingebrigtsen
2011-07-06 18:28   ` Dave Abrahams
2011-07-06 19:55     ` lee [this message]
2011-07-06 20:00     ` Dan Christensen
2011-07-19 16:32     ` 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=87r563xjz0.fsf@yun.yagibdah.de \
    --to=lee@yun.yagibdah.de \
    --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).