From: Steve Purcell <steve@sanityinc.com>
To: "Mattias Engdegård" <mattias.engdegard@gmail.com>
Cc: 72829@debbugs.gnu.org, Stefan Kangas <stefankangas@gmail.com>,
Stefan Monnier <monnier@iro.umontreal.ca>
Subject: bug#72829: describe-function NEWS* scraper override
Date: Mon, 9 Sep 2024 15:43:01 +0100 [thread overview]
Message-ID: <0F7EAF42-7F20-4087-8EB6-DA64F1D0E7A0@sanityinc.com> (raw)
In-Reply-To: <9C37E010-B0F8-48EA-9E40-8E26A17BC929@gmail.com>
Yep, happy to discuss. The case for removals is that some symbols were actually removed in one Emacs version and then re-added later.
My overall technique is to load everything that I can, dump all the symbols I found, and then diff those dumps between Emacs versions. Using my nix-emacs-ci builds makes this straightforward to automate.
Not all features shipped with an Emacs build can be loaded in that build, though, because some rely on native or optional features, e.g. Windows or Treesitter. As such, it’s hard to get an authoritative list of all the known symbols.
In practice, the lists I’ve generated have been good enough for package-lint, and I often use the `package-lint-describe-symbol-history` command when I’m curious about a given symbol.
-Steve
prev parent reply other threads:[~2024-09-09 14:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-27 11:35 bug#72829: describe-function NEWS* scraper override Mattias Engdegård
2024-08-31 10:10 ` Eli Zaretskii
2024-08-31 14:06 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-08-31 17:13 ` Mattias Engdegård
2024-08-31 17:43 ` Eli Zaretskii
2024-08-31 22:26 ` Stefan Kangas
2024-09-01 1:20 ` Stefan Monnier via Bug reports for GNU Emacs, the Swiss army knife of text editors
2024-09-01 4:52 ` Eli Zaretskii
2024-09-01 12:01 ` Mattias Engdegård
2024-09-09 14:43 ` Steve Purcell [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=0F7EAF42-7F20-4087-8EB6-DA64F1D0E7A0@sanityinc.com \
--to=steve@sanityinc.com \
--cc=72829@debbugs.gnu.org \
--cc=mattias.engdegard@gmail.com \
--cc=monnier@iro.umontreal.ca \
--cc=stefankangas@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 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.