From: Drew Adams <drew.adams@oracle.com>
To: Christopher Dimech <dimech@gmx.com>, moasenwood@zoho.eu
Cc: help-gnu-emacs@gnu.org
Subject: RE: Setting keybinding for org-support-shift-select t
Date: Sun, 4 Oct 2020 10:08:47 -0700 (PDT) [thread overview]
Message-ID: <3713af7f-9c34-4ed9-8f51-acc912344bb2@default> (raw)
In-Reply-To: <trinity-f84b29f4-4c0a-446a-822c-432538145ce7-1601830674219@3c-app-mailcom-bs04>
> The following gives me problems if I have keybindings associated
> with <f1> such as "<f1> q" to display agenda
>
> (global-set-key [f1] #'execute-extended-command)
It's not clear to me what you're asking/saying.
But yes, if `f1' is defined as a prefix key, and
you then instead bind it to a command (and not
to a keymap), then it's no longer a prefix key.
It either is or isn't a prefix key. If bound to
`execute-extended-command' then it's not, so
`f1 q' won't work - as soon as you hit `f1' the
command `execute-extended-command' is invoked.
If bound to a prefix key, when you hit `f1' Emacs
waits for you to hit one or more additional keys,
to complete the key sequence.
next prev parent reply other threads:[~2020-10-04 17:08 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 [this message]
2020-10-04 17:36 ` Christopher Dimech
2020-10-04 17:52 ` Drew Adams
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=3713af7f-9c34-4ed9-8f51-acc912344bb2@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).