From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Gregory Heytings <gregory@heytings.org>
Cc: help-gnu-emacs@gnu.org
Subject: Re: PROPOSAL: Repurpose one key (why only one?) and reserve it for third-party packages
Date: Wed, 17 Feb 2021 09:07:02 +0000 [thread overview]
Message-ID: <87pn0z12rt.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <51e726ab000a1191c27a@heytings.org> (message from Gregory Heytings on Mon, 15 Feb 2021 11:08:30 +0000)
Gregory Heytings <gregory@heytings.org> writes:
>>
>> I'm not sure I understand your point here. Any single key that's picked
>> will have a similar limitation.
>>
>
> With a single key you indeed have a limitation, but it's the limitation of
> the keyboard, not an arbirary one. You have full access to all letters,
> all digits, all symbols, combined or not with the control and/or meta
> modifier. That's a lot more than 26 or 52 keys.
I see what you mean but I don't think it's a huge difference. Most
desktop keyboards have ~104 keys. And some of those can't be
differentiated from each other by Emacs. Laptop keyboards usually have
fewer, mine has 81.
>> For example, let's suppose that M-o is picked. That's my favourite, I
>> know you don't like it.
>>
>
> It's in the proposal, it would be a perfect choice, together with C-o.
I think C-o is a terrible idea. Open-line is a very useful command.
It's useful in all sorts of text editing scenarios. Yes, the same can
be done using return and C-b, but that's longer.
In my opinion, M-o is a good idea though. The M-o prefix is only really
useful in enriched mode. Perhaps it could be retained in that mode
only.
BR,
Robert Thorpe
next prev parent reply other threads:[~2021-02-17 9:07 UTC|newest]
Thread overview: 74+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <7ef75c33936136eb3a20@heytings.org>
[not found] ` <8735y56naf.fsf@posteo.net>
[not found] ` <8ed9b43502ae9a36b057@heytings.org>
[not found] ` <87tuqk6d9d.fsf@posteo.net>
[not found] ` <3966473cc1ab9f104724@heytings.org>
2021-02-10 23:35 ` PROPOSAL: Repurpose one key and reserve it for third-party packages Philip K.
2021-02-11 8:45 ` Gregory Heytings
2021-02-11 13:53 ` Philip K.
2021-02-11 15:47 ` Philip K.
2021-02-11 15:59 ` Gregory Heytings
2021-02-11 16:20 ` Philip K.
2021-02-11 17:48 ` Gregory Heytings
2021-02-11 18:34 ` Philip K.
2021-02-11 21:15 ` Gregory Heytings
2021-02-11 22:48 ` Philip K.
2021-02-12 0:01 ` Gregory Heytings
2021-02-12 10:27 ` Philip K.
2021-02-12 11:59 ` Gregory Heytings
2021-02-12 13:23 ` Philip K.
2021-02-12 13:54 ` Gregory Heytings
2021-02-12 14:09 ` Philip Kaludercic
2021-02-12 16:04 ` Gregory Heytings
2021-02-12 17:25 ` Philip Kaludercic
2021-02-12 17:54 ` Gregory Heytings
2021-02-12 18:16 ` Philip Kaludercic
2021-02-12 21:48 ` Gregory Heytings
2021-02-13 0:37 ` Philip Kaludercic
2021-02-13 8:33 ` Gregory Heytings
2021-02-13 9:09 ` Philip Kaludercic
2021-02-13 13:06 ` Gregory Heytings
2021-02-13 14:28 ` Philip Kaludercic
2021-02-13 15:01 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 16:08 ` Philip Kaludercic
2021-02-13 15:02 ` Gregory Heytings
2021-02-13 15:21 ` Jean Louis
2021-02-13 15:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 15:39 ` Nothing is the list - " Jean Louis
2021-02-13 20:14 ` Philip Kaludercic
2021-02-13 20:58 ` Jean Louis
2021-02-13 21:18 ` Gregory Heytings
2021-02-13 21:32 ` Philip Kaludercic
2021-02-13 21:37 ` PROPOSAL: Repurpose one key (why only one?) " Jean Louis
2021-02-13 23:55 ` Philip Kaludercic
2021-02-14 6:19 ` Jean Louis
2021-02-14 6:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 8:06 ` Jean Louis
2021-02-14 18:30 ` [External] : " Drew Adams
2021-02-14 19:21 ` Jean Louis
2021-02-14 19:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 23:30 ` Drew Adams
2021-02-15 0:33 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-15 5:59 ` Jean Louis
2021-02-14 17:59 ` Gregory Heytings
2021-02-14 18:14 ` libraries (was: Re: PROPOSAL: Repurpose one key (why only one?) and reserve it for third-party packages) Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 18:23 ` PROPOSAL: Repurpose one key (why only one?) and reserve it for third-party packages Philip Kaludercic
2021-02-14 21:37 ` Gregory Heytings
2021-02-15 0:28 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-15 5:02 ` Robert Thorpe
2021-02-15 11:08 ` Gregory Heytings
2021-02-17 9:07 ` Robert Thorpe [this message]
2021-02-20 17:50 ` Gregory Heytings
2021-02-14 18:30 ` [External] : " Drew Adams
2021-02-14 18:50 ` Gregory Heytings
2021-02-14 19:24 ` Jean Louis
2021-02-14 19:41 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-14 23:30 ` [External] : " Drew Adams
2021-02-13 10:05 ` PROPOSAL: Repurpose one key " Jean Louis
2021-02-13 8:24 ` Jean Louis
2021-02-13 12:44 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 14:26 ` Jean Louis
2021-02-13 15:09 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 15:24 ` Jean Louis
2021-02-13 15:38 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-02-13 15:45 ` Jean Louis
2021-02-12 4:45 ` Robert Thorpe
2021-02-12 9:58 ` Philip K.
2021-02-11 16:59 ` [External] : " Drew Adams
2021-02-11 16:58 ` Drew Adams
2021-02-11 16:59 ` Leo Butler
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn0z12rt.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=gregory@heytings.org \
--cc=help-gnu-emacs@gnu.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 read-only IMAP folder(s) and NNTP newsgroup(s).