From: Katsumi Yamaoka <yamaoka@jpl.org>
Cc: ding@gnus.org
Subject: Re: message-add-action problem
Date: Thu, 21 Apr 2005 15:20:58 +0900 [thread overview]
Message-ID: <b9yvf6gtzud.fsf@jpl.org> (raw)
In-Reply-To: <vxkacnsai8t.fsf@mesquite.charcoal.com>
>>>>> In <vxkacnsai8t.fsf@mesquite.charcoal.com> Karl Kleinpaste wrote:
> No Gnus v0.3, XEmacs 21.5.20.
> For a very long time, I've been doing message composition in a separate
> frame, using code I got from someone (unremembered, regrets) on this list:
> ; destroy the composition frame on any kind of exit from composition.
> (defun delete-frame-unless-tty ()
> (if (equal (console-type) 'x)
> (delete-frame)))
> (message-add-action 'delete-frame-unless-tty 'exit 'postpone 'kill)
[...]
> However, since I upgraded to No v0.3, my message composition frames
> are not deleted on send/kill/postpone any more.
> message-mode's define-derived-mode in message.el is destroying the
> global value of message-*-actions by making them all locals and
> aggressively setting them to nil. This can't possibly be correct,
> unless these variables were never meant to be user-accessible. That
> was not my understanding.
AFAIK, message-*-actions were all buffer-local over nine years.
> When I tweak message-mode to re-assert those variables' values in the
> make-local, the basic idea seems to come back...except that it's my
> main Gnus frame that gets deleted, leaving the composition frame,
> exactly the wrong effect. (But that frame now shows *Summary*.)
So, that is just what we have to do. I'm sorry not to have time
to analyze your code, but I'm satisfied with mine:
ftp://ftp.jpl.org/pub/elisp/message-multiple-frames.el.gz
or http://www.jpl.org/ftp/pub/elisp/message-multiple-frames.el.gz
It also might be incomplete, though.
next prev parent reply other threads:[~2005-04-21 6:20 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 [this message]
2005-04-21 15:53 ` Karl Kleinpaste
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=b9yvf6gtzud.fsf@jpl.org \
--to=yamaoka@jpl.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).