Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: Re: Quoting the active region when doing `S W' ?
Date: Thu, 10 Jan 2008 00:05:15 +0100	[thread overview]
Message-ID: <v9hchmr45w.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <b4mhchobkfx.fsf@jpl.org>

On Tue, Jan 08 2008, Katsumi Yamaoka wrote:

> However, the prefix argument for the `R' command in the summary
> buffer has a different meaning.  I'd like to suggest adding
> `SW' (gnus-article-wide-reply-with-original)
> and removing the prefix argument from `g-a-reply-with-original'.
> Objections?

I'm not sure if I understand the differences in the old and new
behavior of `C-u R' and `S W'.

The behavior of `C-u R' was:

  Summary: Reply to author of the current article,
           citing the next 4 articles.
           Ignore active region.

  Article: Reply to all (wide reply),
           citing the current article.
           Ignore active region.

The behavior of `S W' was:

  Summary: Reply to all (wide reply),
           citing the current article.
           Ignore active region.

  Article: Ditto.

Correct?  Could you summarize the new behavior, too, and point out the
differences, please?

I think the ChangeLog entry might more clear with the following
changes.  May I change it?

| -	* gnus-art.el (gnus-article-send-map): New keymap for S prefix keys;
| -	bind SW key to gnus-article-wide-reply-with-original; set default
| +	* gnus-art.el (gnus-article-send-map): New keymap for `S' prefix keys;
| +	bind `S W' to gnus-article-wide-reply-with-original; set default
|  	binding to gnus-article-read-summary-send-keys.
|  	(gnus-article-read-summary-keys): Fix the order of keys; display
|  	continuation keys correctly in the echo area; describe bindings
| -	correctly when keys end with C-h.
| +	correctly when keys end with `C-h'.

Bye, Reiner.
-- 
       ,,,
      (o o)
---ooO-(_)-Ooo---  |  PGP key available  |  http://rsteib.home.pages.de/




  parent reply	other threads:[~2008-01-09 23:05 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 [this message]
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
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=v9hchmr45w.fsf@marauder.physik.uni-ulm.de \
    --to=reinersteib+gmane@imap.cc \
    --cc=Reiner.Steib@gmx.de \
    --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).