unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: kf <gebser@mousecar.com>
To: goncholden <goncholden@protonmail.com>,
	goncholden via Users list for the GNU Emacs text editor
	<help-gnu-emacs@gnu.org>
Subject: Re: Fastest way for users to change between functionalities
Date: Thu, 16 Jun 2022 10:13:04 -0400	[thread overview]
Message-ID: <d410c844-6965-3e08-8d4b-7d6d32d6a0b3@mousecar.com> (raw)
In-Reply-To: <g2iXtob8bWJIQpG6DIBYJzff-8WQ5d2hyqGLRjfKtob6pcIt-v6kw5WL5Y-BjJVKu0k8-rpx7CVAfTNnY7RqHi_-7Ce4whT3xVGlgvZSKmY=@protonmail.com>

On 6/11/22 2:34 AM, goncholden via Users list for the GNU Emacs text 
editor wrote:
> What would be the fastest way for users to change between several modes of functionalities?
> 
> Minibuffer selections? Function calling with keybinding can be difficult because one needs keys to bind them to. When one has many packages enabled, it is difficult to find what good keybinding to use.

It can be difficult to determine a keybinding which thereafter will be 
intuitive.  I imagine being in the situation to use it and think about 
where my fingers want to go.  I also think of similarities to similar 
functionalities.

Once having thought of candidates, I use C-h k <candidate keybinding> to 
find if that keybinding is already defined (is already being used by 
some other functionality).  If it's not already defined, then it can be 
used.

It's a bit more work, but I also add the keybinding to a menu so that 
(1) a mouseclick can invoke that funcitonality, and (2) I can easily 
find what the keybinding is later when I've forgotten it.  :)

hth



      reply	other threads:[~2022-06-16 14:13 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-11  6:34 Fastest way for users to change between functionalities goncholden via Users list for the GNU Emacs text editor
2022-06-16 14:13 ` kf [this message]

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=d410c844-6965-3e08-8d4b-7d6d32d6a0b3@mousecar.com \
    --to=gebser@mousecar.com \
    --cc=goncholden@protonmail.com \
    --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).