From: Christopher Dimech <dimech@gmx.com>
To: Michael Heerdegen <michael_heerdegen@web.de>
Cc: Help GNU Emacs <help-gnu-emacs@gnu.org>, Jean Louis <bugs@gnu.support>
Subject: Re: Which modifier to use?
Date: Mon, 7 Dec 2020 01:35:10 +0100 [thread overview]
Message-ID: <trinity-ba10397c-6b1b-44a8-8850-da4c354caabb-1607301310955@3c-app-mailcom-bs11> (raw)
In-Reply-To: <875z5ebjcl.fsf@web.de>
> Sent: Monday, December 07, 2020 at 12:33 AM
> From: "Michael Heerdegen" <michael_heerdegen@web.de>
> To: "Jean Louis" <bugs@gnu.support>
> Cc: "Help GNU Emacs" <help-gnu-emacs@gnu.org>
> Subject: Re: Which modifier to use?
>
> Jean Louis <bugs@gnu.support> writes:
>
> > Maybe CapsLk can be used as modifier or prefix key?
>
> I think a lot of Emacs users do that. I made it the hyper modifier.
>
> Modifiers can also be combined, so each modifier actually doubles the
> set of keys, given that one can memorize all of the available modifier
> combinations (I can't).
You can make a help function that summarises your keybindings. You can also
executing functions directly aiding your memory with icomplete.
> Michael.
>
>
next prev parent reply other threads:[~2020-12-07 0:35 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
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 [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=trinity-ba10397c-6b1b-44a8-8850-da4c354caabb-1607301310955@3c-app-mailcom-bs11 \
--to=dimech@gmx.com \
--cc=bugs@gnu.support \
--cc=help-gnu-emacs@gnu.org \
--cc=michael_heerdegen@web.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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.