From: Eli Zaretskii <eliz@gnu.org>
To: Panagiotis Koutsourakis <kutsurak@slartibartfast.net>
Cc: rpluim@gmail.com, 60859-done@debbugs.gnu.org
Subject: bug#60859: [PATCH] Remove reference to the kbd function from documentation
Date: Sat, 21 Jan 2023 09:52:23 +0200 [thread overview]
Message-ID: <835yd0miiw.fsf@gnu.org> (raw)
In-Reply-To: <874jspj6fn.fsf@panoramix.zarniwoop.org> (message from Panagiotis Koutsourakis on Tue, 17 Jan 2023 21:40:28 +0200)
> From: Panagiotis Koutsourakis <kutsurak@slartibartfast.net>
> Cc: rpluim@gmail.com, 60859@debbugs.gnu.org
> Date: Tue, 17 Jan 2023 21:40:28 +0200
>
> On Tue, Jan 17 2023, Eli Zaretskii wrote:
>
> >
> > 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.
>
> Eli, I am not sure if you saw my earlier message with the second
> proposed patch taking into account your feedback from yesterday.
> Apologies for any confusion I caused.
>
> Robert raised some valid points in his reply about it:
>
> 1. it does not describe accurately the arguments accepted by the old API:
> lisp strings and vectors of input events are missing. I think that
> pointing the users to the reference manual is enough to remedy this.
>
> 2. The syntax accepted by the new API and 'kbd' is not explicit. This
> is, I believe, a more serious issue. I don't think that the previous
> versions of the manual had an explicit description of it at this point,
> but since we are re-examining the section anyway, we should write a few
> words. I adapted the description Robert wrote in his e-mail (thank you
> Robert!).
>
> I am attaching the patch with these changes.
Thanks, installed on the emacs-29 branch (with some changes), and
closing the bug.
prev parent reply other threads:[~2023-01-21 7:52 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
2023-01-17 19:40 ` Panagiotis Koutsourakis
2023-01-21 7:52 ` 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
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=835yd0miiw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60859-done@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).