From: Hendrik Tews <hendrik.tews@kernkonzept.com>
To: Richard Stallman <rms@gnu.org>,
Lars Ingebrigtsen <larsi@gnus.org>,
45438@debbugs.gnu.org
Subject: bug#45438: 27.1; please fix misleading documentation for assoc-delete-all
Date: Sat, 26 Dec 2020 22:04:00 +0100 [thread overview]
Message-ID: <87sg7sgtz3.fsf@cert.kernkonzept.com> (raw)
In-Reply-To: <E1kt6no-0002VV-Ma@fencepost.gnu.org> (Richard Stallman's message of "Sat, 26 Dec 2020 05:28:00 -0500")
Hi,
> Whether it is worth doing the work to make it better, I have no
> opinion. Maybe it is better to do other work instead.
There is a connection to bug#45437, which see.
I agree that it is questionable to go back in time and annotate
all functions with precise information when they had been added.
However, I believe you should
- change your development process such that, in the future, version
information for functions and variables is recorded
- not ignorantly closing issues such as 45437, when a couple of
people spent several hours to debug a problem that takes you
only 5 minutes to fix. Or how long will it take you to add one
sentence to the documentation of make-temp-file? Or how many
hours of other people do you want to waste by saving 5 minutes
on your side?
I now and then contribute to Proof General, which aims to support
about 3 major emacs version. Please advise how one can develop
backward compatible elisp code when the version in the function
documentation is non-present, plain wrong or misleading.
Best regards,
Hendrik
next prev parent reply other threads:[~2020-12-26 21:04 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-25 22:13 bug#45438: 27.1; please fix misleading documentation for assoc-delete-all Hendrik Tews
2020-12-25 22:32 ` Lars Ingebrigtsen
2020-12-26 10:28 ` Richard Stallman
2020-12-26 10:58 ` Eli Zaretskii
2020-12-26 21:56 ` Lars Ingebrigtsen
2020-12-27 5:38 ` Richard Stallman
2020-12-27 17:47 ` Eli Zaretskii
2020-12-28 5:25 ` Richard Stallman
2020-12-26 21:04 ` Hendrik Tews [this message]
2020-12-26 21:17 ` Hendrik Tews
[not found] <<87zh21fsb3.fsf@cert.kernkonzept.com>
[not found] ` <<87blehcyai.fsf@gnus.org>
[not found] ` <<E1kt6no-0002VV-Ma@fencepost.gnu.org>
[not found] ` <<834kk8n8a8.fsf@gnu.org>
2020-12-26 18:59 ` Drew Adams
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=87sg7sgtz3.fsf@cert.kernkonzept.com \
--to=hendrik.tews@kernkonzept.com \
--cc=45438@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=rms@gnu.org \
/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).