Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+from-uce@imap.cc>
To: Holger Sparr <sparr@mfkrs1.mw.tu-dresden.de>,
	Didier Verna <didier@xemacs.org>
Cc: <ding@gnus.org>, bugs@gnus.org
Subject: Re: nndiary documentation bug
Date: Thu, 03 May 2007 20:54:41 +0200	[thread overview]
Message-ID: <v9mz0lu49a.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <lnwszpc061.fsf@mfk.tu-dresden.de> (Holger Sparr's message of "Thu\, 03 May 2007 19\:00\:22 +0200")

On Thu, May 03 2007, Holger Sparr wrote:

> From (info "(gnus)Running NNDiary") : 
>
> ,----
> |    In order to use `nndiary' in autonomous mode, you have several
> | things to do:
> | 
> |    * Allow `nndiary' to retrieve new mail by itself.  Put the following
> |      line in your `gnusrc' file:
> | 
> |           (setq nndiary-get-new-mail t)
> `----
>
> This seems to be no longer true.
>
> By now, `nndiary-get-new-mail' is actually designed as a server variable
> and should therefor be used like this:
>
> (setq gnus-secondary-select-methods '((nndiary "" 
>                                                (nndiary-get-new-mail t))))

I think Holger is right.  Didier, what do you think?

BTW, is there any reason _not_ to include (info "(gnus)Running
NNDiary") in the stable branch (v5-10)?

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



       reply	other threads:[~2007-05-03 18:54 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <lnwszpc061.fsf@mfk.tu-dresden.de>
2007-05-03 18:54 ` Reiner Steib [this message]
2007-05-07 13:10   ` Didier Verna
2007-05-07 14:29     ` Holger Sparr
2007-05-09  7:13       ` Didier Verna
2007-05-07 16:32     ` Reiner Steib
2007-05-09  7:03       ` Didier Verna
2007-05-09  9:30         ` Kamen TOMOV

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=v9mz0lu49a.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+from-uce@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --cc=bugs@gnus.org \
    --cc=didier@xemacs.org \
    --cc=ding@gnus.org \
    --cc=sparr@mfkrs1.mw.tu-dresden.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).