unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Richard Stallman <rms@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 49631@debbugs.gnu.org
Subject: bug#49631: 28.0.50; dired-hide-details-mode Probably introduced at or before Emacs version 24.4
Date: Tue, 20 Jul 2021 20:52:12 -0400	[thread overview]
Message-ID: <E1m60T6-0005Yv-8P@fencepost.gnu.org> (raw)
In-Reply-To: <838s227bv2.fsf@gnu.org> (message from Eli Zaretskii on Mon, 19 Jul 2021 14:59:45 +0300)

[[[ To any NSA and FBI agents reading my email: please consider    ]]]
[[[ whether defending the US Constitution against all enemies,     ]]]
[[[ foreign or domestic, requires you to follow Snowden's example. ]]]

  > The feature works by searching the etc/NEWS* files, and finding a
  > symbol there doesn't necessarily mean the Emacs release in which it's
  > mentioned is the actual release where the symbol was introduced.

I think we can implement an efficient, accurate, automatic way to
determine which release each function appeared in.

We could run a script on each Emacs release to find all the function
definitions in it, then make a sorted list of their names.  By
comparing these, we can find for each function the first release it
was defined in.

We only need to scan each release once, all in the same way.  We would
scan the old releases at the start, and scan each new release when it
is made, adding new functions to the records.

There could be a few functions for which that does not give correct
results, as they were defined in weird ways.  We could add those
functions manually to the records.  Since they won't be many, we could
afford to do that by hand.

Scanning a new release will never alter the information about
functions in previous releases, so once we have fixed an exception, it
will stay fixed.

We don't have to include these records in the release.  It's enough to
compare them with the results of checking the NEWS files.  Then
generate a file listing the exceptions: functions whose first release
differs from the result obtained by checking NEWS files.  It should be
short.

help-fns--first-release could check that file of exceptions first.

Then it could state its results as exact, not an approximation.

-- 
Dr Richard Stallman (https://stallman.org)
Chief GNUisance of the GNU Project (https://gnu.org)
Founder, Free Software Foundation (https://fsf.org)
Internet Hall-of-Famer (https://internethalloffame.org)







  parent reply	other threads:[~2021-07-21  0:52 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-19  0:08 bug#49631: 28.0.50; dired-hide-details-mode Probably introduced at or before Emacs version 24.4 Richard Stallman
2021-07-19 11:59 ` Eli Zaretskii
2021-07-19 13:57   ` Lars Ingebrigtsen
2021-09-29 11:48     ` Stefan Kangas
2021-09-29 11:54       ` Steve Purcell
2021-07-21  0:52   ` Richard Stallman [this message]
2021-07-21 11:31     ` Eli Zaretskii
2021-07-21 16:04     ` Lars Ingebrigtsen
2021-07-21 16:15       ` Lars Ingebrigtsen

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=E1m60T6-0005Yv-8P@fencepost.gnu.org \
    --to=rms@gnu.org \
    --cc=49631@debbugs.gnu.org \
    --cc=eliz@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).