From: Katsumi Yamaoka <yamaoka@jpl.org>
To: ding@gnus.org
Subject: Re: `S V' behaves differently in Article buffer
Date: Tue, 26 Jun 2007 16:32:54 +0900 [thread overview]
Message-ID: <b4m8xa7maqh.fsf@jpl.org> (raw)
In-Reply-To: <b4msl8gmcmg.fsf@jpl.org>
>>>>>> In <m2y7i8iady.fsf@sl392.st-edmunds.cam.ac.uk> Leo wrote:
>> Doing `S V' (gnus-summary-very-wide-reply-with-original) in Article
>> buffer is different than in summary buffer:
>> o it does not switch to the mail buffer
Fixed in the trunk. In addition, incomplete summary command keys
followed by `C-h' now invoke `describe-bindings' as usual. Try
`S C-h' for example in the article buffer.
In addition, I've fixed a bug that prevents XEmacs from working.
(The third argument of `pop-to-buffer' is incompatible between
Emacs and XEmacs.)
>> o The minibuffer displays "Mark set" when there seems to be no mark
>> set
Mark exists at the end (or possibly the beginning) of the yanked
message. Setting a mark is necessary to make the cite function
(which is specified by the `message-cite-function' variable) work.
prev parent reply other threads:[~2007-06-26 7:32 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-25 10:41 Leo
2007-06-25 12:39 ` Katsumi Yamaoka
2007-06-26 7:32 ` 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=b4m8xa7maqh.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=ding@gnus.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).