From: Eli Zaretskii <eliz@gnu.org>
To: Jean Louis <bugs@gnu.support>
Cc: emacs-devel@gnu.org
Subject: Re: Obtaining a database of new functionality per Emacs version
Date: Thu, 10 Dec 2020 16:14:43 +0200 [thread overview]
Message-ID: <83mtyl4ujw.fsf@gnu.org> (raw)
In-Reply-To: <X9HOxmvxd9r/YH9W@protected.rcdrun.com> (message from Jean Louis on Thu, 10 Dec 2020 10:31:18 +0300)
> Date: Thu, 10 Dec 2020 10:31:18 +0300
> From: Jean Louis <bugs@gnu.support>
>
> * Vasilij Schneidermann <mail@vasilij.de> [2020-12-07 16:30]:
> > Hello everyone,
> >
> > I'm looking into creating a tool helping me with ensuring that my
> > packages actually support the Emacs versions they claim to by
> > highlighting uses of unsupported functions/variables [1].
>
> If one could launch automatically various Emacs versions and obtain a
> list of all functions and all variables, by also keeping those flags
> if variable is obsolete or not, or function is obsolete or not, then
> such lists could be exported for each Emacs version and their
> differences easily found.
You do realize that Vasilij wanted to know ab out _all_ the functions,
not just those present in "emacs -Q"? To do what he wanted, you'd
need to load all of the Emacs packages as well, one by one, taking
care to unload them or restart the session, to account for basic
incompatibilities between some of them. I don't think this is a
practical solution.
next prev parent reply other threads:[~2020-12-10 14:14 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-07 12:23 Obtaining a database of new functionality per Emacs version Vasilij Schneidermann
2020-12-07 15:19 ` Stefan Monnier
2020-12-07 18:11 ` Vasilij Schneidermann
2020-12-07 18:20 ` Eli Zaretskii
2020-12-07 19:54 ` Stefan Monnier
2020-12-07 15:34 ` Eli Zaretskii
2020-12-07 17:50 ` Vasilij Schneidermann
2020-12-07 18:17 ` Eli Zaretskii
2020-12-07 20:08 ` Stefan Monnier
2020-12-07 20:25 ` Eli Zaretskii
2020-12-07 20:40 ` Stefan Monnier
2020-12-10 7:31 ` Jean Louis
2020-12-10 14:14 ` Eli Zaretskii [this message]
2020-12-10 16:47 ` Stefan Monnier
2020-12-10 17:22 ` Vasilij Schneidermann
2020-12-10 17:59 ` Stefan Monnier
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=83mtyl4ujw.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=bugs@gnu.support \
--cc=emacs-devel@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).