Re: mail-sources backend specific?

[kai.grossjohann@gmx.net (Kai Großjohann)]

prj@po.cwru.edu (Paul Jarc) writes:

> nnmaildir does not use nnoo, and its server parameters are not
> prefixed with "nnmaildir-".  It does not use global variables to
> represent its server parameters.  So there is no problem here:

Well, err, it sounds as if the mail-sources trick wouldn't work for
nnmaildir in that case.

Sounds like a rather complicated situation.  Maybe we could introduce
something like gnus-group-find-parameter (or was it
gnus-group-get-parameter?) for server `variables'?  Then all places
would say (mumble 'mail-sources) instead of mail-sources, and mumble
would know to look in the server first, and then in the global
variable.

But that would require large-scale changing of the source.

Hm.

Oh!  There is already a mechanism for local variables -- the
buffers.  So do people think it would work to set the variables local
to the right buffers?

Another possibility might be to wrap calls to interesting functions
in a macro which constructs a let form that binds all variables to
the server parameters, if server parameters do indeed exist.

Complicated.  I don't like it.  But I think it's just the current
design.  Is there a chance for making it more sane?

I think what Gnus needs is an OOPS.
-- 
OOA: object-oriented analysis
OOD: object-oriented design
OOPS: object-oriented mistakes