From: Richard Stallman <rms@gnu.org>
To: michael@cadilhac.name (Michaël Cadilhac)
Cc: emacs-devel@gnu.org, ding@gnus.org
Subject: Re: report-emacs-bug and *mail* buffer.
Date: Sun, 11 Mar 2007 21:27:50 -0400 [thread overview]
Message-ID: <E1HQZKI-0006hW-La@fencepost.gnu.org> (raw)
In-Reply-To: <87fy8bsxtp.fsf@lrde.org> (michael@cadilhac.name)
=2D message-user-agent, which calls `message-mail', ignores its
SWITCH-FUNCTION and CONTINUE args and always open a new buffer.
Isn't that a bug? Shouldn't message-mail obey these arguments?
next parent reply other threads:[~2007-03-12 1:27 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87mz2pt92d.fsf@lrde.org>
[not found] ` <E1HQFbl-0001tK-20@fencepost.gnu.org>
[not found] ` <87fy8bsxtp.fsf@lrde.org>
2007-03-12 1:27 ` Richard Stallman [this message]
2007-03-12 4:24 ` Katsumi Yamaoka
2007-03-12 6:40 ` Miles Bader
2007-03-12 19:18 ` Richard Stallman
2007-03-13 0:59 ` Katsumi Yamaoka
2007-03-14 3:25 ` Richard Stallman
2007-03-14 9:12 ` Katsumi Yamaoka
2007-03-14 11:48 ` Katsumi Yamaoka
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=E1HQZKI-0006hW-La@fencepost.gnu.org \
--to=rms@gnu.org \
--cc=ding@gnus.org \
--cc=emacs-devel@gnu.org \
--cc=michael@cadilhac.name \
/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).