From: TRS-80 <lists.trs-80@isnotmyreal.name>
To: help-gnu-emacs@gnu.org
Subject: Re: Which modifier to use?
Date: Sat, 05 Dec 2020 16:29:39 -0500 [thread overview]
Message-ID: <2d40cc5817c659d9d4b502fc359f6c12@isnotmyreal.name> (raw)
In-Reply-To: <AM0PR06MB657761F81265ACDCDF2DC6E696F00@AM0PR06MB6577.eurprd06.prod.outlook.com>
> On 2020-12-05 10:03, Arthur Miller wrote:
>
> I leave Super to my window manager and xbindkeys; and all other
> modifiers go to applications. It is a rule. Makes life easier if you
> switch between Windows and GNU/Linux
Luckily I can avoid Windoze nearly 100% of the time nowadays, however I
still follow this rule and think it's a great idea, anyway.
I use i3 (wm) and have lots of custom keybindings at the OS/WM level,
they are all based on using Super as modifier. So, in my mind, Super
(aka "Win") has to do with window manager.
Inside Emacs, I also group related keybindings behind a sort of "leader"
key, for example (dk here is alias for define-key, stricty to shorten
these lines so I can keep nice formatting):
(dk global-map (kbd "C-c y") '("Yankpad" . nil))
(dk global-map (kbd "C-c y c") '("Capture" .
yankpad-capture-snippet))
(dk global-map (kbd "C-c y e") '("Edit" .
yankpad-edit))
(dk global-map (kbd "C-c y i") '("Insert" .
yankpad-insert))
(dk global-map (kbd "C-c y r") '("Reload" .
yankpad-reload))
(dk global-map (kbd "C-c y R") '("Repeat" .
yankpad-repeat))
(dk global-map (kbd "C-c y s") '("Set (local) category" .
yankpad-set-local-category))
(dk global-map (kbd "C-c y S") '("Set (global) category" .
yankpad-set-category))
I think it is little known that you can define keys in this way, I
learned it while setting up which-key. If you use that package, the car
of the alist will appear as the description, allowing you to create sort
of poor man's menu system. :)
Cheers,
TRS-80
next prev parent reply other threads:[~2020-12-05 21:29 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-05 11:28 Which modifier to use? Jean Louis
2020-12-05 11:48 ` Christopher Dimech
2020-12-05 12:55 ` Jean Louis
2020-12-05 15:03 ` Arthur Miller
2020-12-05 17:55 ` Jean Louis
2020-12-05 21:29 ` TRS-80 [this message]
2020-12-06 5:40 ` Jean Louis
2020-12-05 12:25 ` Stefan Möding
2020-12-05 12:59 ` Jean Louis
2020-12-05 15:52 ` Drew Adams
2020-12-05 16:08 ` Arthur Miller
2020-12-05 18:01 ` Jean Louis
2020-12-05 14:55 ` Arthur Miller
2020-12-05 17:54 ` Jean Louis
2020-12-06 9:14 ` Marcin Borkowski
2020-12-07 6:57 ` Jean Louis
2020-12-06 23:33 ` Michael Heerdegen
2020-12-07 0:35 ` Christopher Dimech
2020-12-09 7:13 ` Philip K.
-- strict thread matches above, loose matches on Subject: below --
2020-12-05 22:34 arthur miller
2020-12-05 22:58 ` TRS-80
2020-12-06 0:58 ` arthur miller
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=2d40cc5817c659d9d4b502fc359f6c12@isnotmyreal.name \
--to=lists.trs-80@isnotmyreal.name \
--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).