unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>
Cc: help-gnu-emacs@gnu.org, moasenwood@zoho.eu
Subject: RE: RE: Setting keybinding for org-support-shift-select t
Date: Sun, 4 Oct 2020 10:52:05 -0700 (PDT)	[thread overview]
Message-ID: <94858e0d-61f9-4e33-9c53-24ad39b0aab9@default> (raw)
In-Reply-To: <trinity-b4cbdc08-ffb9-46c0-9cd6-83db5bd5caed-1601832964081@3c-app-mailcom-bs04>

> I have usually used key bindings to do some operations I like. But then,
> the keybindings became too cryptic for me to remember and thought of
> using my user defined function names for the more complicated operations.
> 
> As you are saying, I can either have <f1> defined as a Prefix-Key
> or use it to call my user defined functions.  Hover I cannot use <f1>
> to do both - calling functions and using keybindings.
> 
> So then I might have, for example, <f1> to use with keybindings and
> <f2> to use with my user defined functions.
> 
> Correct me if I am wrong, but I think I understood you.

Yes, I believe you understood.

A key can _either_ be bound to a keymap (and to
a prefix command, which is, in effect, just that
keymap) _or_ be bound to a command (which is not
a prefix command, i.e., not just a keymap).

Removing the parenthetical qualifications: A key
can either be bound to a keymap or to a command,
not to both.

Either Emacs sees only a prefix key and waits for
the rest of a key sequence or Emacs sees a completed
sequence and invokes its command.



  reply	other threads:[~2020-10-04 17:52 UTC|newest]

Thread overview: 27+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-10-04 10:55 Setting keybinding for org-support-shift-select t Christopher Dimech
2020-10-04 11:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 11:31   ` Christopher Dimech
2020-10-04 11:49     ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 11:52       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 12:25         ` Christopher Dimech
2020-10-04 12:40           ` 2QdxY4RzWzUUiLuE
2020-10-04 12:54             ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 14:03             ` Christopher Dimech
2020-10-04 15:02               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 16:19                 ` Christopher Dimech
2020-10-04 18:57                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 19:26                     ` Christopher Dimech
2020-10-04 19:34                       ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 16:57                 ` Christopher Dimech
2020-10-04 17:08                   ` Drew Adams
2020-10-04 17:36                     ` Christopher Dimech
2020-10-04 17:52                       ` Drew Adams [this message]
2020-10-04 18:10                         ` Christopher Dimech
2020-10-04 19:00                           ` Drew Adams
2020-10-05  3:55                             ` Christopher Dimech
2020-10-05  4:12                               ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 19:16                           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 19:10                   ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 12:48           ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 11:34 ` Emanuel Berg via Users list for the GNU Emacs text editor
2020-10-04 12:14   ` Christopher Dimech

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=94858e0d-61f9-4e33-9c53-24ad39b0aab9@default \
    --to=drew.adams@oracle.com \
    --cc=dimech@gmx.com \
    --cc=help-gnu-emacs@gnu.org \
    --cc=moasenwood@zoho.eu \
    /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).