From: Eli Zaretskii <eliz@gnu.org>
To: Hong Xu <hong@topbug.net>
Cc: 74999@debbugs.gnu.org
Subject: bug#74999: [PATCH v4] Use `keymap*-set' over `global-set-key'/`define-key' in elisp intro
Date: Fri, 27 Dec 2024 09:44:39 +0200 [thread overview]
Message-ID: <868qs1y3h4.fsf@gnu.org> (raw)
In-Reply-To: <87h66qp0c2.fsf@topbug.net> (message from Hong Xu on Thu, 26 Dec 2024 14:05:01 -0800)
> From: Hong Xu <hong@topbug.net>
> Date: Thu, 26 Dec 2024 14:05:01 -0800
>
> On 2024-12-26 Thu 13:46 GMT-08, Hong Xu <hong@topbug.net> wrote:
>
> > * doc/lispintro/emacs-lisp-intro.texi (Key Bindings): Since
> > `global-set-key' and `define-key' are considered legacy, we encourage
> > `keymap-global-set' and `keymap-set' now.
> > ---
> > <...>
> >
> > +@findex global-unset-key
> > +Historically, keys are unbound globally using a lower-function,
> > +@code{global-unset-key}, which is now considered legacy. Its key
> > +binding format follows that of @code{global-set-key}. The above key
> > +unbinding example can be rewritten as:
> > +@smallexample
> > +@group
> > +;;; Unbind 'C-x f'
> > +(global-unset-key "\C-xf")
> > +@end group
> > +@end smallexample
> > +
>
> I'm thinking about dropping this paragraph, because `global-unset-key'
> isn't commonly seen, and there's no point to over fill an introduction
> with less used functions. Please advice.
I wouldn't remove it. This manual is an extended tutorial of the
Emacs Lisp language, so it doesn't necessarily include only the
frequently-used functions. We must trust the author of this manual,
who was a great expert in teaching Emacs Lisp, that his decision to
include this function had a good reason.
next prev parent reply other threads:[~2024-12-27 7:44 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-12-19 22:36 bug#74983: [PATCH] Use `keymap-set' instead of `define-key' in emacs lisp intro Hong Xu
2024-12-20 7:01 ` Eli Zaretskii
2024-12-20 9:35 ` Stefan Kangas
2024-12-20 21:42 ` bug#74999: [PATCH v2] Recommend " Hong Xu
2024-12-21 7:19 ` Eli Zaretskii
2024-12-21 8:03 ` bug#74999: [PATCH v3] " Hong Xu
2024-12-23 20:42 ` Hong Xu
2024-12-24 3:27 ` Eli Zaretskii
2024-12-26 8:20 ` Eli Zaretskii
2024-12-26 21:46 ` bug#74999: [PATCH v4] Use `keymap*-set' over `global-set-key'/`define-key' in elisp intro Hong Xu
2024-12-26 22:05 ` Hong Xu
2024-12-27 7:44 ` Eli Zaretskii [this message]
2024-12-26 21:58 ` bug#74999: [PATCH v3] Recommend `keymap-set' instead of `define-key' in emacs lisp intro Hong Xu
2024-12-27 7:37 ` Eli Zaretskii
2024-12-21 8:06 ` bug#74999: [PATCH v2] " Hong Xu
2024-12-20 15:43 ` bug#74983: [PATCH] Use " Drew Adams via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-12-20 21:50 ` Hong Xu
2024-12-21 7:20 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=868qs1y3h4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=74999@debbugs.gnu.org \
--cc=hong@topbug.net \
/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.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.