Gnus development mailing list
 help / color / mirror / Atom feed
From: Reiner Steib <reinersteib+gmane@imap.cc>
To: ding@gnus.org
Subject: nnmairix and nnir key bindings
Date: Sat, 14 Jun 2008 16:54:27 +0200	[thread overview]
Message-ID: <v9ej709ie4.fsf@marauder.physik.uni-ulm.de> (raw)

Hi,

I start anew thread about key bindings of the (new) Gnus search
facilities, nnir.el and nnmairix.el.

From an earlier discussion...

In article <kz4pbud4ae.fsf@kafka.physik3.gwdg.de>, on Feb 27 2008, David wrote:
| Reiner Steib <reinersteib+gmane@imap.cc> writes:
|> We also want to install nnir.el soon.  nnir.el uses `G G' (only a
|> single binding).  (And there's contrib/gnus-namazu.el which uses `C-c
|> C-n' when `gnus-namazu-insinuate' is called).  Maybe we should think
|> about using some two key stroke prefix for mail search facilities (I'm
|> not sure if it makes sense to use nnir.el and nnmairix.el at the same
|> time).
|
| Some people might want to use nnir.el e.g. for IMAP and nnmairix.el for
| locally stored archive groups, so it should be possible to use both.
|
|> For the Group mode, we could use e.g. `G b', `G B' or `G G' as prefix
|> for (mail) search.  In the Summary mode, we may use the same prefix or
|> a different one.  I don't have a strong opinion on this.  (`G b' runs
|> `gnus-summary-best-unread-article', but it is also on `,', so we may
|> steal this or move it to `G B'.)  Opinions?
|
| Using the same prefix in group and summary mode is a good idea.

Here are three alternatives.  I'd suggest to go for (a).  Opinions?
Other suggestions?

(a) Establish `G G' as a prefix for all search facilities in Gnus.
    `G G' is not used in Gnus upto now (beside nnir.el).

    - Change nnmairix to use the prefix `G G' instead of `G b' in
      group and instead of `$ ...' in summary mode.

      Use `G G m ...' (nn*m*airix) for not so frequently used nnmairix
      commands.
    
    - Change nnir.el's `G G' to some other `G G' prefixed key, e.g. 
      `G G i' (nn*i*r).

(b) Establish `G B' as a prefix for all search facilities in Gnus.
    `G B' is not used in Gnus upto now.

    - Change nnmairix to use the prefix `G B' instead of `G b' in
      group and instead of `$ ...' in summary mode.

      Use `G B m ...' (nn*m*airix) for not so frequently used nnmairix
      commands.
    
    - Change nnir.el's `G G' to some `G B' prefixed key, e.g. `G B i'
      (nn*i*r).

(c) Establish `G b' as a prefix for all search facilities in Gnus.
    `G b' is used in Gnus for `gnus-summary-best-unread-article'.

    - Change nnmairix to use the prefix `G b' instead of `$ ...' in
      summary mode.

      Use `G b m ...' (nn*m*airix) for not so frequently used nnmairix
      commands.
    
    - Change nnir.el's `G G' to some `G b' prefixed key, e.g. `G b i'
      (nn*i*r).

    - Move the `G b' binding of `gnus-summary-best-unread-article' to
      `G B'.

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



             reply	other threads:[~2008-06-14 14:54 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-06-14 14:54 Reiner Steib [this message]
2008-06-15 19:15 ` David Engster

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