all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Jean Louis <bugs@gnu.support>
To: emacs-devel@gnu.org
Subject: Re: Obtaining a database of new functionality per Emacs version
Date: Thu, 10 Dec 2020 10:31:18 +0300	[thread overview]
Message-ID: <X9HOxmvxd9r/YH9W@protected.rcdrun.com> (raw)
In-Reply-To: <X84ewTWkQRrdHJhK@odonien.localdomain>

* 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. Process could be automated and lists of
functions and variables could be included in Emacs package that could
help new packages to know if some function or variable is not
compatible with some versions.

Jean



  parent reply	other threads:[~2020-12-10  7:31 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 [this message]
2020-12-10 14:14   ` Eli Zaretskii
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=X9HOxmvxd9r/YH9W@protected.rcdrun.com \
    --to=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 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.