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

[-- Attachment #1: Type: text/plain, Size: 2012 bytes --]

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

> Anyway, I'll make an effort to implement SWITCH-FUNCTION and
> CONTINUE arguments in Gnus.

Done.  I have not committed it yet, though.  The patch to the
v5-10 branch is attached.  It can also be applied to the Gnus
trunk with a slight hand work.

Now `gnus-user-agent' and `message-user-agent' regard CONTINUE
and SWITCH-FUNCTION arguments.  For instance, whenever you eval
the following form, you will be brought to the message buffer
named "*mail to whom*":

(let ((mail-user-agent 'gnus-user-agent))
  (compose-mail "whom" nil nil t 'pop-to-buffer))

If `message-mail-user-agent' is set to a certain agent, Message
passes SWITCH-FUNCTION and CONTINUE arguments to that agent.
For example, this lets Gnus use `sendmail-user-agent' to compose
a mail:

(let ((mail-user-agent 'gnus-user-agent)
      (message-mail-user-agent 'sendmail-user-agent))
  (compose-mail "whom" nil nil t 'pop-to-buffer))

Furthermore, I slightly changed the meaning of the nil value of
`message-generate-new-buffers' and made the value t the same as
the value `unique'.  While the nil value made a buffer with a
name such as "*mail message*" formerly, it now uses a name as
what the value `unique' uses, like "*mail to whom*".
The difference between nil and `unique' is that nil uses an
existing message buffer if any but `unique' always uses a new
message buffer.  This fits the name of the variable, doesn't it?
Note that nil distinguishes the buffer "*mail to whom*" from the
buffer "*mail*".  In other words, the value nil never uses the
existing buffer named "*mail*" when it is made to use the buffer
named "*mail to whom*".  The new value `standard' is similar to
nil but is for those who like simpler "*mail message*" names.

If there's no comment, I will install those changes.

In addition, I've also revised message-multiple-frames.el so as
to agree those changes.  It is avalable at:
ftp://ftp.jpl.org/pub/elisp/ or http://www.jpl.org/ftp/pub/elisp/

Regards,


[-- Attachment #2: message_el.patch.gz --]
[-- Type: application/x-gzip, Size: 2734 bytes --]

[-- Attachment #3: Type: text/plain, Size: 142 bytes --]

_______________________________________________
Emacs-devel mailing list
Emacs-devel@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-devel

      parent reply	other threads:[~2007-03-14 11:48 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
2007-03-14 11:48             ` Katsumi Yamaoka [this message]

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=b4mhcso82rt.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).