From: Eli Zaretskii <eliz@gnu.org>
To: Stefan Kangas <stefan@marxist.se>
Cc: dhan1thri@gmail.com, 55647@debbugs.gnu.org
Subject: bug#55647: Emacs manual - Change references to "global-set-key" to "keymap-global-set"
Date: Wed, 08 Jun 2022 05:34:29 +0300 [thread overview]
Message-ID: <83leu76fyi.fsf@gnu.org> (raw)
In-Reply-To: <CADwFkmnSG1k2dwQpb5JJ3ya+H7j9vz8k_5EJaEcHS+FMd=VPWQ@mail.gmail.com> (message from Stefan Kangas on Tue, 7 Jun 2022 17:35:09 -0500)
> From: Stefan Kangas <stefan@marxist.se>
> Date: Tue, 7 Jun 2022 17:35:09 -0500
> Cc: Dhanvanthri N <dhan1thri@gmail.com>, 55647@debbugs.gnu.org
>
> Eli Zaretskii <eliz@gnu.org> writes:
>
> >> I'm not sure how to find all the references to global-set-key in the
> >> documentation;
> >
> > Grep the *.texi files in the doc/lispref/ and doc/emacs/ directories
> > of the Emacs source tree for the references to the obsolete functions
> > and commands.
>
> I think there are quite a few of these.
>
> However, I'm not sure that there is a strong need to change them for
> Emacs 29 -- at least not in the user documentation. Users might be
> consulting Emacs 29 documentation, yet still want to use their Init file
> on Emacs 28 or older.
>
> How about waiting with updating all of this documentation on master
> until after Emacs 29 has been released?
The question is actually whether we indeed consider global-set-key and
friends obsolete. If we do, we should at least document the modern
replacements and say that the obsolete ones are obsolete. Leaving the
documentation as-is without reference to obsolescence is not a good
idea, IMO.
prev parent reply other threads:[~2022-06-08 2:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-25 23:16 bug#55647: Emacs manual - Change references to "global-set-key" to "keymap-global-set" dhanvanthri
2022-05-26 5:32 ` Eli Zaretskii
[not found] ` <328e75e7-49b0-ee5a-3432-eb4d81659377@gmail.com>
2022-05-29 5:45 ` Eli Zaretskii
2022-06-07 22:35 ` Stefan Kangas
2022-06-08 2:34 ` Eli Zaretskii [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83leu76fyi.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=55647@debbugs.gnu.org \
--cc=dhan1thri@gmail.com \
--cc=stefan@marxist.se \
/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.