Gnus development mailing list
 help / color / mirror / Atom feed
From: Katsumi Yamaoka <yamaoka@jpl.org>
To: rms@gnu.org
Cc: ding@gnus.org, michael@cadilhac.name, emacs-devel@gnu.org
Subject: Re: report-emacs-bug and *mail* buffer.
Date: Wed, 14 Mar 2007 18:12:47 +0900	[thread overview]
Message-ID: <b4md53c9oj4.fsf@jpl.org> (raw)
In-Reply-To: <E1HRK6u-0007LJ-Ge@fencepost.gnu.org>

>>>>> In <E1HRK6u-0007LJ-Ge@fencepost.gnu.org> Richard Stallman wrote:

>> 		     although I think it doesn't solve the problem
>>     that `sendmail-user-agent' overrides an existing *mail* buffer.

>> I am not sure what that means, or whether it is really a problem,
>> but it is certainly a different issue.  If you want to raise it,
>> please send a bug report about it.

>     That's what Michaël Cadilhac reported in <87fy8bsxtp.fsf@lrde.org>.
>     Or I misunderstood it?

> I think there is some sort of misunderstanding here, but I don't
> know what it is.  87fy8bsxtp.fsf@lrde.org does not seem to say
> anything about this.  It talks about whether `new' is implemented
> in OTHER mail user agents.

We might have seen the report from a different viewpoint, but I
could reproduce exactly the problem:

>>>>> In <87mz2pt92d.fsf@lrde.org> Michaël Cadilhac wrote:

> Create a new mail with Gnus with `m'. The buffer is called `*mail*'.
> Now use M-x report-emacs-bug : your Gnus mail is converted to
> mail-mode and asked for deletion. Even if you say no to deletion, the
> buffer is converted to mail-mode, but if you really want to make a bug
> report, you can't until you've close your Gnus *mail*.

The causes are:

1. A user leaves `mail-user-agent' the default, which is
   `sendmail-user-agent', even if he is a Gnus user.

2. `report-emacs-bug' calls `sendmail-user-agent-compose' by way
   of `compose-mail' because of `sendmail-user-agent'.

3. `sendmail-user-agent-compose' calls `mail', and `mail' runs
   `mail-mode' unconditionally in the *mail* buffer having
   already existed.

Michaël Cadilhac's patch makes `report-emacs-bug' give the symbol
`new' as the fourth argument CONTINUE to `compose-mail'.  A non-nil
value of CONTINUE is normally used to reuse an existing *mail*
buffer in order to compose a mail.  However, the value `new' is
special in at least `sendmail-user-agent-compose' and `mail'.
It has not been documented AFAIK, but it makes `mail' use a new
*mail* buffer.  It indeed solves the problem, but I wrote:

>>>>> In <b4m1wjvf5ru.fsf@jpl.org> Katsumi Yamaoka wrote:

> Anyway, that Gnus users set `mail-user-agent' to `gnus-user-agent'
> is the best, I think.

Regards,

  reply	other threads:[~2007-03-14  9:12 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
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 [this message]
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=b4md53c9oj4.fsf@jpl.org \
    --to=yamaoka@jpl.org \
    --cc=ding@gnus.org \
    --cc=emacs-devel@gnu.org \
    --cc=michael@cadilhac.name \
    --cc=rms@gnu.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).