From: Katsumi Yamaoka <yamaoka@jpl.org>
Subject: Re: message-add-action problem
Date: Fri, 22 Apr 2005 09:46:11 +0900 [thread overview]
Message-ID: <b9yy8bbzlik.fsf@jpl.org> (raw)
In-Reply-To: <vxkr7h4nn1m.fsf@mesquite.charcoal.com>
>>>>> In <vxkr7h4nn1m.fsf@mesquite.charcoal.com> Karl Kleinpaste wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> AFAIK, message-*-actions were all buffer-local over nine years.
> No. I have 5.10.3 lying around, and its message.el, with mod date of
> 14 June 2003, makes these local (for purpose of adding some one-time
> eval forms), but does not nil them out. So the effect is that one's
> preferred actions are combined with the one-time forms.
> I just tried running that 5.10.3, and it works as expected other than
> that it, too, deletes the wrong frame. This is evidently an Xemacs
> 21.5 difficulty.
I see. I found out Lars had changed `message-mode' so as to set
those variables as nil.
2003-10-16 Lars Magne Ingebrigtsen <larsi@gnus.org>
* message.el (message-inserted-headers): New variable.
(message-mode): Make local.
(message-mode): Set all the local action variables to nil.
I guess Lars considered there may be those who invoke the
message-mail command from the message-mode buffer. In that
case, message-*-actions will get excessive (or possibly harmful)
values in the second message buffer. I think it can be improved
as follows:
(set (make-local-variable 'message-*-actions)
(default-value 'message-*-actions))
I don't think we should do that because the doc-strings for
those variables don't begin with "*", though.
next prev parent reply other threads:[~2005-04-22 0:46 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-21 4:03 Karl Kleinpaste
2005-04-21 6:20 ` Katsumi Yamaoka
2005-04-21 15:53 ` Karl Kleinpaste
2005-04-22 0:46 ` Katsumi Yamaoka [this message]
2005-04-22 3:00 ` Karl Kleinpaste
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=b9yy8bbzlik.fsf@jpl.org \
--to=yamaoka@jpl.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).