From: David Engster <deng@randomsample.de>
To: ding@gnus.org
Subject: Re: gnus shouldn't be making general-purpose variables buffer-local
Date: Wed, 17 Dec 2008 14:38:26 +0100 [thread overview]
Message-ID: <kzljuely5p.fsf@randomsample.de> (raw)
In-Reply-To: <b4moczbhtsn.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 17 Dec 2008 21:26:16 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>>>>>> David Engster wrote:
>> So maybe, we should change `gnus-summary-set-local-parameters' to only
>> set those variables buffer-local that begin with a proper prefix, like
>> "gnus-" and "mm-" ?
>
> But it will disable the existing features concerning the parameters
> of which the names don't begin with "gnus-" and "mm-".
That shouldn't happen, since those parameters are usually retrieved
through `gnus-group-get-parameter', `gnus-group-fast-parameter', or
`gnus-group-find-parameter' (see e.g. how nnimap uses the uidvalidity
parameter). If an existing feature breaks because of that change, I
would argue that it is broken, since it shouldn't depend on group
parameters being buffer-local variables.
In short: Making a group parameter buffer-local should only be done for
overriding a global value.
That gives me an idea: in `gnus-summary-set-local-parameters', instead
of defining fixed prefixes like "gnus-" or "mm-", we could simply make
only those parameters buffer-local which are globally bound?
> The best way seems to be to add "gnus-" or "mm-" to all the
> parameters. However, it will take time for coding and verifying.
The main problem I see is that this is an incompatible change,
i.e. parameters from existing groups would have to be updated.
> Maybe, it should do after the Emacs 23.1 release.
I agree in any case.
Regards,
David
next prev parent reply other threads:[~2008-12-17 13:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-12-12 6:42 Ami Fischman
2008-12-16 17:22 ` Ted Zlatanov
2008-12-16 22:54 ` Katsumi Yamaoka
2008-12-17 8:46 ` David Engster
2008-12-17 9:20 ` Katsumi Yamaoka
2008-12-17 10:21 ` Katsumi Yamaoka
2008-12-22 17:36 ` Ted Zlatanov
2008-12-22 18:55 ` Reiner Steib
2008-12-22 20:53 ` Ami Fischman
2008-12-24 2:32 ` Katsumi Yamaoka
2008-12-17 11:10 ` David Engster
2008-12-17 12:26 ` Katsumi Yamaoka
2008-12-17 13:38 ` David Engster [this message]
2008-12-17 14:28 ` David Engster
2008-12-17 23:22 ` Katsumi Yamaoka
2008-12-18 0:19 ` David Engster
-- strict thread matches above, loose matches on Subject: below --
2008-11-02 17:47 Ami Fischman
2008-12-10 7:02 ` Xavier Maillard
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=kzljuely5p.fsf@randomsample.de \
--to=deng@randomsample.de \
--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).