From: Emanuel Berg via Users list for the GNU Emacs text editor <help-gnu-emacs@gnu.org>
To: help-gnu-emacs@gnu.org
Subject: Re: define-key for fortran code
Date: Sat, 29 May 2021 16:37:43 +0200 [thread overview]
Message-ID: <877djhr4g8.fsf@zoho.eu> (raw)
In-Reply-To: trinity-44a85d08-3763-42cf-a18d-a40f497e3f3a-1622294325664@3c-app-mailcom-bs01
jaime-escalante wrote:
> I cannot follow how to use your function
>
> (define-key f90-mode-map key fun)
>
> I was passing the key sequence as (kbd "H-o q"), you are
> using "key" and just pass "q" to it. Could I just pass "H-o
> q" to it?
Why ever `define-key' would not behave like a normal defun
I don't know so why ever not?
However I'd rather pass "\H-oq" - if indeed H-o has been
defined as a prefix command. And you can find out by just
evaling the string, here "\H-oq" - for me it says
elisp--preceding-sexp: Invalid modifier in string
so here, it hasn't.
--
underground experts united
https://dataswamp.org/~incal
prev parent reply other threads:[~2021-05-29 14:37 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-28 17:47 define-key for fortran code jaime-escalante
2021-05-29 4:23 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 12:13 ` ludvig-faddeev
2021-05-29 12:25 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 13:18 ` jaime-escalante
2021-05-29 14:24 ` Robert Thorpe
2021-05-29 14:32 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 16:55 ` pauline-galea
2021-05-29 20:03 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 16:39 ` ludvig-faddeev
2021-05-29 20:00 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 17:20 ` ludvig-faddeev
2021-05-29 20:04 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 17:44 ` Jean Louis
2021-05-29 20:06 ` Emanuel Berg via Users list for the GNU Emacs text editor
2021-05-29 14:37 ` Emanuel Berg via Users list for the GNU Emacs text editor [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=877djhr4g8.fsf@zoho.eu \
--to=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).