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 09:46:37 +0100 [thread overview]
Message-ID: <87vdtj41ux.fsf@engster.org> (raw)
In-Reply-To: <b4mvdtjive8.fsf@jpl.org> (Katsumi Yamaoka's message of "Wed, 17 Dec 2008 07:54:07 +0900")
Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> On Thu, 11 Dec 2008 22:42:39 -0800 "Ami Fischman" <ami@fischman.org> wrote:
>>>>> Gnus makes 'timestamp a buffer-local variable in *Summary* buffers
>>>>> (and, I suspect, any other set group parameter). This causes buggy
>>>>> interaction with non-gnus (async, usually) functions that bind
>>>>> 'timestamp as a function-local variable, such as emacs-jabber's
>>>>> jabber-history-log-message. For the details please see
>>>>> http://thread.gmane.org/gmane.emacs.devel/105256. Can gnus be changed
>>>>> to prefix such buffer-locals with at least gnus- or, better yet,
>>>>> gnus-summary-<group-name>- ?
There are indeed lots of possible group parameters which turn to
buffer-local variables. I am surely not innocent here, with nnmairix
having group parameters like `query', `folder' and `threads'. The
problem I see is that changing those is incompatible with existing
groups... not sure how to deal with that...
> Well, how can I get `timestamp' as a buffer-local variable in
> the summary buffer?
I have some nnimap groups with `timestamp' in their group parameters,
but don't know which feature put it there. You can search for
`timestamp' in your .newsrc.eld.
> So far I found neither such a variable nor
> a way to make Gnus make it.
>
> C-h v timestamp RET
> => [No match]
You would have to bind it globally first to see that it's buffer-local.
Regards,
David
next prev parent reply other threads:[~2008-12-17 8:46 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 [this message]
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
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=87vdtj41ux.fsf@engster.org \
--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).