From: Daiki Ueno <ueno@unixuser.org>
To: ding@gnus.org
Subject: Re: [gnus git] branch master updated: n0-13-65-gece58ab =2= Autoload `password-in-cache-p'. ; Try to fix XEmacs message-options buffer-local issue.
Date: Sun, 06 Mar 2011 07:55:12 +0900 [thread overview]
Message-ID: <87lj0txjn3.fsf@broken.deisui.org> (raw)
In-Reply-To: <m3r5alrf7t.fsf@quimbies.gnus.org> (Lars Magne Ingebrigtsen's message of "Sat, 05 Mar 2011 12:15:02 +0100")
Lars Magne Ingebrigtsen <larsi@gnus.org> writes:
> Julien Danjou <julien@danjou.info> writes:
>
>>> I'm not quite sure I understand the issue. Since the variable is now
>>> buffer-local, do we need to bind it at all?
>>
>> AFAIU, yes, if you use a temp buffer (in XEmacs).
>
> Right. Daiki Ueno's patch to copy over the buffer-local variables to
> the temp buffer might solve that problem, though?
My patch is not enough, since there are several places Gnus binds
message-options:
$ grep -n '(message-options ' *.el
gnus-art.el:4954: (message-options message-options)
gnus-art.el:8444: (let ((message-options message-options))
gnus-int.el:697: (let ((message-options message-options))
gnus-int.el:720: (let ((message-options message-options))
gnus-sum.el:10348: (message-options message-options)
message.el:1862:;; (let ((message-options message-options)) ...)
message.el:4091: (message-options message-options))
mml.el:1469: (message-options message-options)
In theory, we could probably change the code like:
(let ((tmp-message-options message-options))
(set-buffer ...)
(setq message-options tmp-message-options))
everywhere listed above and also do this in functions called within the
let-bindings. Too much work with little return, IMHO :)
Regards,
--
Daiki Ueno
next prev parent reply other threads:[~2011-03-05 22:55 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <E1Pusj3-0004c4-00@quimby.gnus.org>
2011-03-03 10:44 ` Julien Danjou
2011-03-03 11:20 ` Ted Zlatanov
2011-03-03 11:27 ` Julien Danjou
2011-03-03 22:27 ` Daiki Ueno
2011-03-04 9:50 ` Julien Danjou
2011-03-04 12:32 ` Daiki Ueno
2011-03-04 14:56 ` Ted Zlatanov
2011-03-05 10:28 ` Lars Magne Ingebrigtsen
2011-03-05 11:07 ` Julien Danjou
2011-03-05 11:15 ` Lars Magne Ingebrigtsen
2011-03-05 22:55 ` Daiki Ueno [this message]
2011-03-15 17:32 ` Lars Magne Ingebrigtsen
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=87lj0txjn3.fsf@broken.deisui.org \
--to=ueno@unixuser.org \
--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).