From: Reiner Steib <reinersteib+gmane@imap.cc>
Subject: Re: Key prefix reserved for users in Gnus
Date: Sat, 15 Apr 2006 19:02:39 +0200 [thread overview]
Message-ID: <v9zmim4vrk.fsf@marauder.physik.uni-ulm.de> (raw)
In-Reply-To: <m3u08y9g37.fsf@quimbies.gnus.org>
On Thu, Apr 13 2006, Lars Magne Ingebrigtsen wrote:
> Reiner Steib <reinersteib+gmane@imap.cc> writes:
>
>> I do the same, but I wouldn't recommend it to novice users. The main
>> point is that we can guarantee that Gnus won't bind `v' in the future.
>
> True, but do we want to? It's the final unused key [...],
`v' is the only one (beside `y') that is left in all important Gnus
modes (group, summary, server). There are still some lower case
letters left in group mode. In summary only v, y and z.
> and we may want to use it for something new and spiffy we invent at
> some point.
If it's so spiffy, we could get rid of some duplicate binding (most of
the single letter keys still have a binding in some other map) of a
less spiffy feature¹. Reserving `v' gives the user the possibility to
bind feature important to him/her to simple key such as `v a' ... `v
z'.
Bye, Reiner.
¹ E.g., I can't recall that I ever used these summary keys either
because I only remember some other binding (b - K v, u - !) or
because I never used the command (i, w).
b gnus-article-view-part
i gnus-summary-news-other-window
u gnus-summary-tick-article-forward
w gnus-summary-stop-page-breaking
--
,,,
(o o)
---ooO-(_)-Ooo--- | PGP key available | http://rsteib.home.pages.de/
next prev parent reply other threads:[~2006-04-15 17:02 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-01-25 14:39 Reiner Steib
2006-01-26 7:18 ` Glyn Millington
2006-04-09 12:37 ` Reiner Steib
2006-04-12 15:31 ` Lars Magne Ingebrigtsen
2006-04-12 16:38 ` Reiner Steib
2006-04-13 5:53 ` Lars Magne Ingebrigtsen
2006-04-14 19:29 ` Miles Bader
2006-04-15 17:02 ` Reiner Steib [this message]
2006-04-15 18:49 ` Lars Magne Ingebrigtsen
2006-04-16 12:55 ` Reiner Steib
2006-04-16 15:04 ` Lars Magne Ingebrigtsen
2006-04-15 23:48 ` Miles Bader
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=v9zmim4vrk.fsf@marauder.physik.uni-ulm.de \
--to=reinersteib+gmane@imap.cc \
--cc=Reiner.Steib@gmx.de \
/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).