Gnus development mailing list
 help / color / mirror / Atom feed
From: kai.grossjohann@gmx.net (Kai Großjohann)
Subject: Re: mail-sources backend specific?
Date: Sat, 03 May 2003 22:57:59 +0200	[thread overview]
Message-ID: <847k97zr1k.fsf@lucy.is.informatik.uni-duisburg.de> (raw)
In-Reply-To: <87znm3g5qz.fsf@wmipf.in-berlin.de>

Michael Teichgräber <mt@wmipf.in-berlin.de> writes:

> kai.grossjohann@gmx.net (Kai Großjohann) writes:
>
>>> This is not what has been expected.
>>
>> What was expected?
>
> s/expected/desired/
>
> It worked as it was told, but it did not result in the behaviour I
> wanted: retrieving local mail for more than one backend.
>
> And, the "mail-sources" entries, that had been inserted into
> nnoo-definition-alist, looked strange. This was because the
> "mail-sources" parameter of the select-method (obviously) didn't have
> a nnfolder- or nnml- prefix (as for other server variables). So the
> first call of nnoo-change-server (for backend nnml) could influence
> the later call (for backend nnfolder) by means of the current
> global "mail-sources" value.

Hm.

But what happens if you have two nnml backends and in both you set a
variable (a parameter?) nnml-foo?  Then the first can influence the
second in the same way, no?

Is there a more serious bug here?

>>> <alternative approach>
>>>
>>> Would it break the design, if mail-sources was handled as server
>>> variable too, so that -- depending on backend -- "nn*-mail-sources"
>>> could be specified?
>>
>> That sounds like a plan.  For completeness, some defvoos might have
>> to be added, but it looks quite nice.
>
> E.g. (defvoo nn*-mail-sources nil) for all backends that retrieve
> mail: nnmh, nnml, nnfolder, nnimap ...

Yep.

>> But OTOH, server variables may be useful for other things, so what do
>> you think about fixing the server variable handling?
>
> With 'fixing' do you mean making it work with variable-value pairs as
> desired some mails before? -- Such as
>
>     (setq gnus-secondary-select-methods 
> 	  '((nnfolder "" (A X)))
> 	    (nnml "" (A Y))) ,
>
> so that A (not having nnfolder-, nnml- prefixes) may have different
> values in contexts of these backends? Or did you refer to my "is not
> what has been expected"?

What I meant is to make 

(setq gnus-secondary-select-methods
      '((nnfolder "" (mail-sources foo))
        (nnml "" (mail-sources bar))))

behave as you (and I) desire: fetch mail from foo for the nnfolder
backend and from bar for the nnml backend.

Maybe it's enough to make the variables local to the current buffer?
But probably it isn't -- Gnus jumps around the buffers a lot.

Maybe it works to let-bind the variables.

-- 
file-error; Data: (Opening input file no such file or directory ~/.signature)



  reply	other threads:[~2003-05-03 20:57 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-04-27 12:22 Using different backends Andreas Jaeger
2003-04-27 15:25 ` Kai Großjohann
2003-04-27 19:06   ` Andreas Jaeger
2003-05-02 13:03     ` Michael Teichgräber
2003-05-02 13:30       ` Kai Großjohann
2003-05-02 14:26         ` Michael Teichgräber
2003-05-02 14:47           ` Kai Großjohann
2003-05-02 15:15             ` Michael Teichgräber
2003-05-03 15:51               ` mail-sources backend specific? (was: Using different backends) Michael Teichgräber
2003-05-03 17:25                 ` mail-sources backend specific? Kai Großjohann
2003-05-03 20:00                   ` Michael Teichgräber
2003-05-03 20:57                     ` Kai Großjohann [this message]
2003-05-04  2:40                       ` Michael Teichgräber
2003-05-04 13:29                         ` Kai Großjohann
2003-05-05 16:38                           ` Paul Jarc
2003-05-06 16:31                             ` Kai Großjohann
2003-05-06 19:55                               ` Paul Jarc
2003-05-29 14:27                                 ` Kai Großjohann
2003-05-29 16:14                                   ` Paul Jarc
2003-10-18 12:53                                     ` Lars Magne Ingebrigtsen
2003-05-03 17:21               ` Using different backends Kai Großjohann
2003-05-03 19:00                 ` Michael Teichgräber
2003-05-03 20:00                   ` Kai Großjohann
2003-04-28 18:58 ` Paul Jarc
2003-04-29  5:45   ` Andreas Jaeger
2003-04-29 15:23     ` Paul Jarc

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=847k97zr1k.fsf@lucy.is.informatik.uni-duisburg.de \
    --to=kai.grossjohann@gmx.net \
    /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).