From: Karl Kleinpaste <karl@charcoal.com>
Subject: Re: message-add-action problem
Date: Thu, 21 Apr 2005 11:53:57 -0400 [thread overview]
Message-ID: <vxkr7h4nn1m.fsf@mesquite.charcoal.com> (raw)
In-Reply-To: <b9yvf6gtzud.fsf@jpl.org> (Katsumi Yamaoka's message of "Thu, 21 Apr 2005 15:20:58 +0900")
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.
> ftp://ftp.jpl.org/pub/elisp/message-multiple-frames.el.gz
> or http://www.jpl.org/ftp/pub/elisp/message-multiple-frames.el.gz
I will take a look. Thanx.
--karl
next prev parent reply other threads:[~2005-04-21 15:53 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 [this message]
2005-04-22 0:46 ` Katsumi Yamaoka
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=vxkr7h4nn1m.fsf@mesquite.charcoal.com \
--to=karl@charcoal.com \
/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).