Gnus development mailing list
 help / color / mirror / Atom feed
From: Mike Kupfer <mike.kupfer@xemacs.org>
To: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: auto auto-expirable
Date: Mon, 01 Jun 2009 19:23:13 -0700	[thread overview]
Message-ID: <12651.1243909393@rawbw.com> (raw)
In-Reply-To: Your message of "Mon, 01 Jun 2009 20:20:00 +0900." <b4my6scjj4v.fsf@jpl.org>

I don't have much experience writing Emacs docstrings, but FWIW here's
an attempt to tighten the wording.  Thanks for making this customizable.

>  :function gnus-group-auto-auto-expirable-p
>  :function-document
>  "Check whether articles that havie been read are automatically marked as expirable when moved to or copied to GROUP."

   "Indicate whether articles that are marked expirable should retain that mark when moved or copied to GROUP."

>  :variable gnus-auto-auto-expirable-newsgroups
>  :variable-default nil
>  :variable-document
>  "Groups in which articles that have been read are automatically marked as expirable when moved to or copied to there.

   "Articles that are moved or copied into these groups will retain the expirable mark.

> If non-nil, this should be a regexp that should match all groups in
> which to perform auto auto-expiry.  If this is nil or the group name
> does not match this, the expirable marks of articles that have been
> read will remain (not be set forcibly) when they are moved to or
> copied to the group in which to perform auto-expiry.  This only makes
> sense for mail groups."

Should that be "If this is nil... the expirable marks of articles will
be cleared"?

>  :variable-group nnmail-expire
>  :variable-type '(choice (const nil)
> 			 regexp)
>  :parameter-type '(const :tag "Automatic Auto-Expire" t)
>  :parameter-document
>  "Article that have been read will be automatically marked as expirable when moved to or copied to this group if this group is set to perform auto-expiry.")

   "Articles that have the expirable mark will retain that mark if moved or copied into a matching group, assuming the group does auto-expiry."

cheers,
mike



  parent reply	other threads:[~2009-06-02  2:23 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-05-29 11:19 Katsumi Yamaoka
2009-05-29 12:08 ` Didier Verna
2009-06-01  3:36 ` Mike Kupfer
2009-06-01  8:35   ` Didier Verna
2009-06-01 11:20     ` Katsumi Yamaoka
2009-06-01 12:47       ` Tim Landscheidt
2009-06-02  2:23       ` Mike Kupfer [this message]
2009-06-02 11:12         ` Katsumi Yamaoka
2009-06-02 11:38           ` Katsumi Yamaoka
2009-06-04  4:13           ` Mike Kupfer
2009-06-13 14:22           ` Tim Landscheidt
2009-08-12  8:28             ` Katsumi Yamaoka
2009-06-02 17:34         ` Reiner Steib
2009-06-05 12:34       ` Greg Troxel

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=12651.1243909393@rawbw.com \
    --to=mike.kupfer@xemacs.org \
    --cc=ding@gnus.org \
    --cc=yamaoka@jpl.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).