From: Xavier Maillard <xma@gnu.org>
To: emacs-jabber-general@lists.sourceforge.net
Cc: ding@gnus.org
Subject: Re: gnus shouldn't be making general-purpose variables buffer-local
Date: Wed, 10 Dec 2008 08:02:05 +0100 [thread overview]
Message-ID: <87iqps7bte.fsf@gnu.org> (raw)
In-Reply-To: <9aa0cfde0811020947m64cdcfe1rb8fb37a5bf84541a@mail.gmail.com>
"Ami Fischman" <ami@fischman.org> writes:
> 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>- ?
Did you ever have a positive answer to your request ?
------------------------------------------------------------------------------
SF.Net email is Sponsored by MIX09, March 18-20, 2009 in Las Vegas, Nevada.
The future of the web can't happen without you. Join us at MIX09 to help
pave the way to the Next Web now. Learn more and register at
http://ad.doubleclick.net/clk;208669438;13503038;i?http://2009.visitmix.com/
next prev parent reply other threads:[~2008-12-10 7:02 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-11-02 17:47 Ami Fischman
2008-12-10 7:02 ` Xavier Maillard [this message]
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
2008-12-17 14:28 ` David Engster
2008-12-17 23:22 ` Katsumi Yamaoka
2008-12-18 0:19 ` David Engster
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=87iqps7bte.fsf@gnu.org \
--to=xma@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-jabber-general@lists.sourceforge.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).