From: Holger Sparr <sparr@mfk.tu-dresden.de>
To: Didier Verna <didier@xemacs.org>
Cc: <ding@gnus.org>
Subject: Re: nndiary documentation bug
Date: Mon, 07 May 2007 16:29:52 +0200 [thread overview]
Message-ID: <ln3b28d7vj.fsf@mfk.tu-dresden.de> (raw)
In-Reply-To: <mux7irk93ue.fsf@uzeb.lrde.epita.fr> (Didier Verna's message of "Mon\, 07 May 2007 15\:10\:33 +0200")
Didier Verna wrote:
> Reiner Steib <reinersteib+from-uce@imap.cc> wrote:
>
>> 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 therefore 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?
>
>
> I don't quite understand the "This seems to be no longer true." part,
> as AFAICR, the design of nndiary-get-new-mail has never changed. I'm
> actually reluctant to advertise this variable as a server one (although
> technically, I guess it's possible to use it that way).
>
> As explained in the doc, nndiary is not a traditionnal mail backend (you
> would not use it for retrieving your emails), so if you want to use it
> in its "autonomous" mode, you probably also have to customize
> nndiary-mail-sources and nndiary-split-methods as well. This is not like
> setting up one *and only one* mail backend as the preferred method for
> getting mails.
I cannot really say when getting new mail for the nndiary backend stopped.
I only guess that it happened after `gnus-server-regenerate-server' for
my nnml backend.
This is what I get now:
,----[ C-h v nndiary-get-new-mail RET ]
| nndiary-get-new-mail is a variable defined in `nndiary.el'.
| Its value is nil
|
|
| Documentation:
| Whether nndiary gets new mail and split it.
| Contrary to traditional mail back ends, this variable can be set to t
| even if your primary mail back end also retreives mail. In such a case,
| NDiary uses its own mail-sources and split-methods.
|
| This is a Gnus server variable. See Info node `(gnus)Select Methods'.
| ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
| [back]
`----
and I assumed something has been changed. Since
,----
| (require 'gnus-diary)
| (setq nndiary-get-new-mail t)
`----
in my .gnus.el has no effect anymore (meaning the default of nil is not changed).
In case it has something to do with my setup, where and how can I investigate?
Holger
next prev parent reply other threads:[~2007-05-07 14:29 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
2007-05-07 13:10 ` Didier Verna
2007-05-07 14:29 ` Holger Sparr [this message]
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=ln3b28d7vj.fsf@mfk.tu-dresden.de \
--to=sparr@mfk.tu-dresden.de \
--cc=didier@xemacs.org \
--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).