From: Katsumi Yamaoka <yamaoka@jpl.org>
To: 14166@debbugs.gnu.org
Cc: Michael Heerdegen <michael_heerdegen@web.de>,
Wolfgang Jenkner <wjenkner@inode.at>
Subject: bug#14166: 24.3.50; report-emacs-bug and mail-user-agent == 'gnus-user-agent
Date: Fri, 12 Apr 2013 16:39:26 +0900 [thread overview]
Message-ID: <b4my5co9p01.fsf@jpl.org> (raw)
In-Reply-To: <87mwt7wzy6.fsf@web.de>
Katsumi Yamaoka wrote:
> Wolfgang Jenkner wrote:
>> On Thu, Apr 11 2013, Stefan Monnier wrote:
>>> more to the point: we start with a call to Gnus's `composefunc' with an
>>> explicit "to" address (with value report-emacs-bug-address). And we end
>>> with a message that uses a different "to" address. So the problem seems
>>> to be on Gnus's side only.
>> The Gnus callee behaves as documented, so you'd normally expect the
>> caller to put up with it. Personally, though, I don't think there's
>> a bug here at all, just an example of legitimate foot-shooting ;-)
> Thanks for your help. I'd like to fix this problem in this manner:
> Background:
> The composefunc of `gnus-user-agent' is `gnus-msg-mail', that is
> called by not only `compose-mail' but also some Gnus internals.
> A posting style corresponding to a currently opened group is
> applied when running `gnus-msg-mail'. No problem if it is used
> within Gnus. However, the posting style may get meaningless or
> harmful if it is called outside of Gnus. This suggests that every
> user will be able to be a foot-shooter.
After having consulted the Gnus code, I changed my mind as follows:
> ・Rename `gnus-msg-mail' to `gnus-msg-mail-1'.
Unnecessary.
> ・Create `gnus-msg-mail' that calls `gnus-msg-mail-1' with `let'-
> binding of `gnus-newsgroup-name' to "gnus-user-agent".
Change this to:
・Make `gnus-msg-mail' `let'-bind `gnus-newsgroup-name' to "".
> ・Use `gnus-msg-mail' for composefunc exclusively. Make Gnus
> internals use `gnus-msg-mail-1' instead of `gnus-msg-mail'.
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
Currently there's no Gnus internal that had better use
`gnus-msg-mail-1' instead of `gnus-msg-mail'.
> ・A user who want to use a posting style even when `compose-mail'
> is used may add it for the group named "gnus-user-agent".
Replace this paragraph with:
・The default posting style, that begins with ".*" and the like,
will be applied to a mail that `compose-mail' originates.
So, what I'm going to do now is simply to modify `gnus-msg-mail'.
Maybe an Info for this is unnecessary.
Regards,
next prev parent reply other threads:[~2013-04-12 7:39 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-09 14:17 bug#14166: 24.3.50; report-emacs-bug and mail-user-agent == 'gnus-user-agent Michael Heerdegen
2013-04-10 5:52 ` Katsumi Yamaoka
2013-04-10 13:39 ` Michael Heerdegen
2013-04-11 0:41 ` Katsumi Yamaoka
2013-04-11 13:51 ` Stefan Monnier
2013-04-11 19:06 ` Wolfgang Jenkner
2013-04-12 1:53 ` Katsumi Yamaoka
2013-04-12 7:39 ` Katsumi Yamaoka [this message]
2013-04-12 15:18 ` Katsumi Yamaoka
2013-04-11 18:03 ` Wolfgang Jenkner
2013-04-11 18:55 ` Michael Heerdegen
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=b4my5co9p01.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=14166@debbugs.gnu.org \
--cc=michael_heerdegen@web.de \
--cc=wjenkner@inode.at \
/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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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 read-only IMAP folder(s) and NNTP newsgroup(s).