From: Eli Zaretskii <eliz@gnu.org>
To: Panagiotis Koutsourakis <kutsurak@slartibartfast.net>
Cc: rpluim@gmail.com, 60859@debbugs.gnu.org
Subject: bug#60859: [PATCH] Remove reference to the kbd function from documentation
Date: Tue, 17 Jan 2023 19:32:34 +0200 [thread overview]
Message-ID: <83lem12hjh.fsf@gnu.org> (raw)
In-Reply-To: <87fsc9jg6p.fsf@panoramix.zarniwoop.org> (message from Panagiotis Koutsourakis on Tue, 17 Jan 2023 18:09:50 +0200)
> Cc: 60859@debbugs.gnu.org
> From: Panagiotis Koutsourakis <kutsurak@slartibartfast.net>
> Date: Tue, 17 Jan 2023 18:09:50 +0200
>
> So, assuming that we want the documentation as a whole to be consistent,
> I see two ways forward: either we eliminate or reduce the importance of
> the old functions in the user manual, or we remove the effective
> deprecation of the old functions in the emacs lisp reference manual and
> expand on the use of 'kbd', 'global-set-key' and 'define-key'.
>
> What do you think?
There's no need to generalize so much. Let's handle this specific
issue, and then move on.
For now, I don't want to remove references to 'kbd' from the manual,
because many people still use it. So please accept that as the
baseline, and let's find the best way to describe the new APIs as
well.
next prev parent reply other threads:[~2023-01-17 17:32 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-16 11:15 bug#60859: [PATCH] Remove reference to the kbd function from documentation Panagiotis Koutsourakis
2023-01-16 14:47 ` Eli Zaretskii
2023-01-16 16:17 ` Panagiotis Koutsourakis
2023-01-16 16:56 ` Eli Zaretskii
2023-01-17 14:20 ` Panagiotis Koutsourakis
2023-01-17 14:56 ` Robert Pluim
2023-01-17 16:09 ` Panagiotis Koutsourakis
2023-01-17 17:16 ` Robert Pluim
2023-01-17 17:32 ` Eli Zaretskii [this message]
2023-01-17 19:40 ` Panagiotis Koutsourakis
2023-01-21 7:52 ` 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
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=83lem12hjh.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60859@debbugs.gnu.org \
--cc=kutsurak@slartibartfast.net \
--cc=rpluim@gmail.com \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).