From: Katsumi Yamaoka <yamaoka@jpl.org>
To: Bastien <bzg@altern.org>
Cc: ding@gnus.org
Subject: Re: Quoting the active region when doing `S W' ?
Date: Thu, 17 Jan 2008 08:09:50 +0900 [thread overview]
Message-ID: <b4mir1t74g1.fsf@jpl.org> (raw)
In-Reply-To: <87y7apqu19.fsf@bzg.ath.cx>
>>>>> Bastien wrote:
> Katsumi Yamaoka <yamaoka@jpl.org> writes:
>> `C-u R' in the article buffer runs wide reply (you can also use
>> a numeric prefix like `1' instead of `C-u'):
> But for me (No Gnus v0.7) `C-u R' didn't make a wide reply.
[...]
You meant `gnus-summary-reply-with-original' which is used in
the *SUMMARY* buffer. In that case, the prefix argument is
interpreted as the number of articles to be replied. I.e.,
since `C-u' is interpreted into 4, `C-u R' means replying to a
series of four articles.
cf. (info "(gnus)Summary Mail Commands")
(info "(gnus)Process/Prefix")
OTOH,
>> (info "(gnus)Article Keymap")
>> ,----
>>| `R'
>>| Send a reply to the current article and yank the current article
>>| (`gnus-article-reply-with-original'). If given a prefix, make a
>>| wide reply. If the region is active, only yank the text in the
>>| region.
>> `----
this is `gnus-article-reply-with-original' which is used in the
*ARTICLE* buffer. In the Gnus CVS trunk, I've changed it so as
not to accept the prefix argument.
,---- [ GNUS-NEWS ]
| ** Now the new command `S W' (`gnus-article-wide-reply-with-original') for
| a wide reply in the article buffer yanks a text that is in the active
| region, if it is set, as well as the `R'
| (`gnus-article-reply-with-original') command. Note that the `R' command
| in the article buffer no longer accepts a prefix argument, which was
| used to make it do a wide reply. *Note Article Keymap::.
`----
Regards,
next prev parent reply other threads:[~2008-01-16 23:09 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-11-22 12:22 Bastien
2007-11-25 21:34 ` Bastien
2007-11-25 23:46 ` Leo
2007-11-26 0:36 ` Bastien
2007-11-26 8:12 ` Leo
2007-12-10 0:50 ` Bastien
2007-12-23 20:50 ` Leo
2008-01-08 11:55 ` Katsumi Yamaoka
2008-01-08 19:52 ` Leo
2008-01-08 22:51 ` Katsumi Yamaoka
2008-01-08 23:12 ` Leo
2008-01-09 22:30 ` Katsumi Yamaoka
2008-01-14 23:40 ` Leo
2008-01-15 0:12 ` Katsumi Yamaoka
2008-01-15 0:23 ` Leo
2008-01-15 1:15 ` Katsumi Yamaoka
2008-01-15 18:50 ` Leo
2008-01-20 14:59 ` Leo
2008-01-09 23:05 ` Reiner Steib
2008-01-09 23:21 ` Katsumi Yamaoka
2008-01-10 8:08 ` Katsumi Yamaoka
2008-01-10 18:55 ` Reiner Steib
2008-01-11 6:48 ` Katsumi Yamaoka
2008-01-11 17:43 ` Reiner Steib
2008-01-15 0:14 ` Katsumi Yamaoka
2008-01-31 11:56 ` Katsumi Yamaoka
2008-01-16 22:34 ` Bastien
2008-01-16 23:09 ` Katsumi Yamaoka [this message]
2008-01-17 13:33 ` Bastien
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=b4mir1t74g1.fsf@jpl.org \
--to=yamaoka@jpl.org \
--cc=bzg@altern.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).