Gnus development mailing list
 help / color / mirror / Atom feed
From: Ted Zlatanov <tzz@lifelogs.com>
To: ding@gnus.org
Subject: Re: gnus shouldn't be making general-purpose variables buffer-local
Date: Mon, 22 Dec 2008 11:36:32 -0600	[thread overview]
Message-ID: <86vdtcf6xr.fsf@lifelogs.com> (raw)
In-Reply-To: <b4mr647ksqa.fsf@jpl.org>

On Wed, 17 Dec 2008 19:21:01 +0900 Katsumi Yamaoka <yamaoka@jpl.org> wrote: 

KY> At least for `timestamp', the attached patch will solve (note
KY> that you need to reload the patched gnus-group.elc because of
KY> `defsubst').  At the first time you enter to a group, the buffer-
KY> local variable `timestamp' is still alive, but it will be renamed
KY> to `gnus-timestamp' when exiting the group.  Maybe the change
KY> will not slow Gnus.

The patch looks OK to me.  It's probably better to do it this way now,
as a bug fix that can go into Gnus and Emacs right away, and do a
thorough fix (as David Engster proposes, IIUC) later.

Thank you for looking into this.

Ted




  reply	other threads:[~2008-12-22 17:36 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 [this message]
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=86vdtcf6xr.fsf@lifelogs.com \
    --to=tzz@lifelogs.com \
    --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).