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: MELPA upgrade error
Date: Fri, 21 Feb 2020 00:15:15 +0100 [thread overview]
Message-ID: <87k14gj1fg.fsf@ebih.ebihd> (raw)
In-Reply-To: jwvlfoxcrux.fsf-monnier+emacs@gnu.org
Stefan Monnier wrote:
>> The trick to obtain the number for the f1
>> fn-key is
>
> There is no "number" for the `f1` key.
As for `help-char', one can test it like this:
(setq help-char 46) ; was 8 which is C-h
(setq help-form (message "help-form executed")) ; was nil
and then type a dot (.) - the number for the
dot char is 46, which can be confirmed with
ascii(1).
Type a dot and you'll see "help-form executed"
executed on the screen. But then, of course,
C-h doesn't work anymore. C-h, or ^H, is 8.
Again use ascii,
$ ascii '^H'
As for [f1], now the functions keys don't work
for me in the Linux VT (well, they could,
I think, with this method [1], but I don't want
them to as to use them would require moving the
hands from the beloved asdf and jkl; positions)
- but for an X instance of Emacs, it should
work inside, outside, and out of the box with
the familiar syntax:
(global-set-key [f1] #'beginning-of-buffer)
[1] https://dataswamp.org/~incal/tty-emacs-keys.txt
--
underground experts united
http://user.it.uu.se/~embe8573
https://dataswamp.org/~incal
next prev parent reply other threads:[~2020-02-20 23:15 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-02-18 0:50 MELPA upgrade error Emanuel Berg via Users list for the GNU Emacs text editor
2020-02-18 7:28 ` VanL
2020-02-18 14:20 ` Stefan Monnier
2020-02-19 1:17 ` VanL
2020-02-20 11:53 ` VanL
2020-02-20 13:26 ` Stefan Monnier
2020-02-20 23:15 ` Emanuel Berg via Users list for the GNU Emacs text editor [this message]
2020-02-21 0:26 ` VanL
2020-02-21 0:48 ` Emanuel Berg via Users list for the GNU Emacs text editor
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=87k14gj1fg.fsf@ebih.ebihd \
--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).