Re: message-add-action problem

[Karl Kleinpaste <karl@charcoal.com>]

Katsumi Yamaoka <yamaoka@jpl.org> writes:
> I found out Lars had changed `message-mode' so as to set
> those variables as nil.
> 	* 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.

It seems unwise to nil them out because then no user settings are ever
useful, which raises the question of why the variables should exist at
all, other than temporary, local items.

> 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.

On that reasoning, would we not also make oodles of -hook variables
equally untouchable?  I doubt that was the intent.  I think such a fix
would be appropriate.

In any event, my particular problem is gone because I have tried your
message-multiple-frames.el and it works quite nicely.  I suggest you
include
        (provide 'message-multiple-frames)
at its end, so that it sits well with the rest of the require/provide
framework used elsewhere in Gnus.

Thank you very much.

--karl