Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org, Daniel Clemente <dcl441-bugs@yahoo.com>
Cc: bugs@gnus.org
Subject: Re: Add nnimap to gnus-auto-subscribed-groups
Date: Fri, 20 Feb 2009 13:05:22 +0100	[thread overview]
Message-ID: <87prhd9uv1.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <878wwnties.fsf@gmail.com> (Daniel Clemente's message of "Mon, 30 Jun 2008 10:51:23 +0200")

On Sat, May 17 2008, Daniel Clemente wrote:
>   the manual says about gnus-auto-subscribed-groups :
>
>> By default this variable makes all new groups that
> come from mail back ends (nnml, nnbabyl, nnfolder,
> nnmbox, nnmh, and nnmaildir) subscribed.
>
>   I think that nnimap should be added there (at the
> manual and at the variable in latest gnus).

On Mon, Jun 30 2008, Daniel Clemente wrote:
>   Could this be done? We have to change the variable and the documentation. Maybe other mail methods should also be included there, not only imap.
>
>   I attach a patch to add nnimap there.

Does anyone see a problem with this change?

> diff -u -r7.66 gnus-start.el
> --- lisp/gnus-start.el	19 May 2008 08:47:42 -0000	7.66
> +++ lisp/gnus-start.el	30 Jun 2008 08:48:49 -0000
> @@ -342,7 +342,7 @@
>    :type 'boolean)
>
>  (defcustom gnus-auto-subscribed-groups
> -  "^nnml\\|^nnfolder\\|^nnmbox\\|^nnmh\\|^nnbabyl\\|^nnmaildir"
> +  "^nnml\\|^nnfolder\\|^nnmbox\\|^nnmh\\|^nnbabyl\\|^nnmaildir\\|^nnimap"
>    "*All new groups that match this regexp will be subscribed automatically.
>  Note that this variable only deals with new groups.  It has no effect
>  whatsoever on old groups.
> cvs server: Diffing pgg
> cvs server: Diffing smilies
> cvs server: Diffing texi
> Index: texi/gnus.texi
> ===================================================================
> RCS file: /usr/local/cvsroot/gnus/texi/gnus.texi,v
> retrieving revision 7.296
> diff -u -r7.296 gnus.texi
> --- texi/gnus.texi	17 Jun 2008 21:37:01 -0000	7.296
> +++ texi/gnus.texi	30 Jun 2008 08:48:59 -0000
> @@ -1348,9 +1348,9 @@
>  more meant for setting some ground rules, while the other variable is
>  used more for user fiddling.  By default this variable makes all new
>  groups that come from mail back ends (@code{nnml}, @code{nnbabyl},
> -@code{nnfolder}, @code{nnmbox}, @code{nnmh}, and @code{nnmaildir})
> -subscribed.  If you don't like that, just set this variable to
> -@code{nil}.
> +@code{nnfolder}, @code{nnmbox}, @code{nnmh}, @code{nnmaildir}, and
> +@code{nnimap}) subscribed.  If you don't like that, just set this
> +variable to @code{nil}.
>
>  New groups that match this regexp are subscribed using
>  @code{gnus-subscribe-options-newsgroup-method}.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/



  parent reply	other threads:[~2009-02-20 12:05 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <284637.62771.qm@web53211.mail.re2.yahoo.com>
     [not found] ` <878wwnties.fsf@gmail.com>
     [not found]   ` <87od4xhco9.fsf@gmail.com>
2008-07-16 20:46     ` David Engster
2009-02-20 12:05   ` Reiner Steib [this message]
2009-02-20 18:26     ` David Engster

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=87prhd9uv1.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=bugs@gnus.org \
    --cc=dcl441-bugs@yahoo.com \
    --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).