From: Van L <van@scratch.space>
To: help-gnu-emacs@gnu.org
Subject: Re: [offtopic] Re: Ctrl-[ ?
Date: Sat, 15 Jun 2019 22:38:46 +1000 [thread overview]
Message-ID: <m2tvcryqeh.fsf@scratch.space> (raw)
In-Reply-To: 20190615094422.GA3890@tuxteam.de
<tomas@tuxteam.de> writes:
> On Sat, Jun 15, 2019 at 07:12:28PM +1000, Van L wrote:
>> Choose the keys comfy for you relative to thumb over modifier key and
>> finger tips poised to strike like in a DOOM Eternal Deathmatch.
>
> It's more complicated than that: on the one hand, there's a strong
> incentive for /one/ default set of keybindings (a baseline, so to
> speak): documentation, tutorials, help forums, etc. (imagine you had
> to parametrize them with $deity-knows-what-weird-keybinding-set, they'd
> spread pretty thinly).
I don't know waht is the proper meaning of the Hyper or Super key
modifier in relation to Emacs. Assuming they are meaningless, using
those don't interfere with the legacy /one/ default set of keybindings.
>> > I'm sure there are multitude of other language-specific keyboard
>> > layouts sharing that weakness...
>>
>> Localise the layout.
>
> See above. I think, realistically, that a non-standard layout is
> (except maybe a few exceptions) a difficult balance act. More than
> it seems at first blush: a key binding set is, after all, like a
> new language -- you get a "tower of Babel" effect if you multiply
> that.
The TCP/IP stack is a 5 or 7 layer tower of babel :-)
My feeling is if you have 50 Emacs people who love Emacs in a boundary
of 50 million people who use Emacs, and the 50 million people can vote
on the most natural comfy feeling layout, which happens to select those
50 people's layout in the first place, the distribution should be big
enough to let users choose from those layouts.
> Now I'm not arguing against using the flexibility Emacs provides
> here, quite on the contrary. I'm just stating that it doesn't come
> at zero cost (on the "social" side).
>
>> > But I didn't want to open /that/ can o' worms -- just to raise
>> > a bit of awareness.
>>
>> I don't have the luxury of 3 modifier keys right of my spacebar and have
>> the following experimental layout. The CAPSLOCK 'on' doesn't function
>> like holding the SHIFT key down for, for example, '(kbd "H-S-l")'.
>
... [snip]
>
> I don't think there's "a solution" to that. It helps being aware of
> the multitude of factors involved.
[ ¯\\_(ツ)_/¯ ]
nuff said
--
© 2019 VanL
gpg using EEF2 37E9 3840 0D5D 9183 251E 9830 384E 9683 B835
'The mouth is the dirtiest part on the human body.' - Bill Wallace
next prev parent reply other threads:[~2019-06-15 12:38 UTC|newest]
Thread overview: 63+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-06 4:49 Ctrl-[ ? Jean-Christophe Helary
2019-06-06 12:58 ` Ralph Seichter
2019-06-06 13:42 ` tomas
2019-06-06 14:08 ` Jean-Christophe Helary
2019-06-06 14:25 ` Stefan Monnier
2019-06-06 15:27 ` Jean-Christophe Helary
2019-06-06 18:29 ` Noam Postavsky
2019-06-06 23:08 ` Jean-Christophe Helary
2019-06-06 23:26 ` Noam Postavsky
2019-06-06 23:35 ` Jean-Christophe Helary
2019-06-07 6:24 ` Eli Zaretskii
2019-06-07 11:43 ` Noam Postavsky
2019-06-07 13:16 ` Jean-Christophe Helary
2019-06-07 22:04 ` Stefan Monnier
2019-06-08 6:22 ` Eli Zaretskii
2019-06-08 14:14 ` Stefan Monnier
2019-06-07 3:36 ` Emanuel Berg via help-gnu-emacs
2019-06-07 4:30 ` Jean-Christophe Helary
2019-06-07 4:43 ` Emanuel Berg via help-gnu-emacs
2019-06-07 5:04 ` Jean-Christophe Helary
2019-06-07 6:15 ` Eli Zaretskii
2019-06-07 8:04 ` Óscar Fuentes
2019-06-07 8:44 ` Eli Zaretskii
2019-06-07 13:19 ` Jean-Christophe Helary
2019-06-07 13:54 ` Noam Postavsky
2019-06-07 14:23 ` Jean-Christophe Helary
2019-06-07 15:17 ` Noam Postavsky
2019-06-07 13:45 ` Óscar Fuentes
2019-06-07 14:20 ` Eli Zaretskii
2019-06-07 18:20 ` Óscar Fuentes
2019-06-07 20:16 ` Eli Zaretskii
2019-06-07 16:30 ` tomas
2019-06-08 0:05 ` Francis Belliveau
2019-06-08 0:31 ` Óscar Fuentes
2019-06-08 8:44 ` tomas
2019-06-08 11:48 ` 조성빈 via help-gnu-emacs
2019-06-08 11:56 ` tomas
2019-06-08 13:06 ` Óscar Fuentes
2019-06-08 13:30 ` Eli Zaretskii
2019-06-08 13:54 ` Jean-Christophe Helary
2019-06-08 14:03 ` tomas
2019-06-08 14:22 ` Jean-Christophe Helary
2019-06-08 15:42 ` Eli Zaretskii
2019-06-09 0:52 ` Jean-Christophe Helary
2019-06-09 6:19 ` Eli Zaretskii
2019-06-09 6:51 ` Jean-Christophe Helary
2019-06-08 13:58 ` tomas
2019-06-08 19:40 ` Óscar Fuentes
2019-06-08 20:09 ` Eli Zaretskii
2019-06-08 20:28 ` tomas
2019-06-08 21:03 ` Francis Belliveau
2019-06-08 21:38 ` Óscar Fuentes
2019-06-09 0:25 ` Stefan Monnier
2019-06-09 1:24 ` Óscar Fuentes
2019-06-18 22:25 ` Stefan Monnier
2019-06-11 23:05 ` Francis Belliveau
2019-06-14 6:51 ` Stefan Monnier
2019-06-14 12:06 ` [offtopic] " Van L
2019-06-14 12:24 ` tomas
2019-06-15 9:12 ` Van L
2019-06-15 9:44 ` tomas
2019-06-15 12:38 ` Van L [this message]
2019-06-09 6:37 ` Eli Zaretskii
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=m2tvcryqeh.fsf@scratch.space \
--to=van@scratch.space \
--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).