unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: "Harald Jörg" <haj@posteo.de>
Cc: Philipp Stephani <phst@google.com>,
	Stefan Monnier <monnier@iro.umontreal.ca>,
	Emacs developers <emacs-devel@gnu.org>
Subject: Re: master 2e090da: Revert commit 1f44a776729adf9c6468a76f8310616fde62eeaa for Flymake.
Date: Mon, 26 Oct 2020 17:58:12 -0700	[thread overview]
Message-ID: <CADwFkmmgqarCDi27E3Jnm4sbdUkmtGy3pwMw_uFkwg+j4JN+fg@mail.gmail.com> (raw)
In-Reply-To: <87mu08wyjo.fsf@hajtower>

haj@posteo.de (Harald Jörg) writes:

>>> Could such an ert-backport.el be a candidate for ELPA?  It should be
>>> useful for all dual-life (Emacs + ELPA) packages.
>>
>> How about just making ert itself into a GNU ELPA core package?
>
> I'd be happy with that.
>
> ert.el would then need to implement some compatibility features itself:
> It uses the new format-prompt, for example, which can be easily covered.
> It also uses backtrace.el, which doesn't exist in Emacs 26.
> backtrace.el, in turn, needs lisp-el-font-lock-keywords-for-backtraces,
> which has been added to lisp-mode.el (in the same commit e09120d6 where
> backtrace.el was created).  I didn't dig any further, but I guess
> there's some effort to unravel all of this.
>
> Maybe it would make sense to _start_ this as a long-term goal right now,
> working for versions 28 and beyond?  That would make ert-backport.el a
> temporary workaround, to be eliminated as soon as versions below 28 go
> out of scope.

Given the amount of work involved (full disclosure: more than I
expected), it sounds like your compatibility package is probably the
better choice for now.  We can think about making ert into a package in
its own right in the future, if we need or want to.

Making ert-backport.el into a GNU ELPA package sounds good to me.  But
let's see if anyone else has any comments.

Thanks for working on this.



  reply	other threads:[~2020-10-27  0:58 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20201025101403.1168.4440@vcs0.savannah.gnu.org>
     [not found] ` <20201025101404.7EBE2204DA@vcs0.savannah.gnu.org>
2020-10-25 13:59   ` master 2e090da: Revert commit 1f44a776729adf9c6468a76f8310616fde62eeaa for Flymake Stefan Monnier
2020-10-26  9:47     ` Harald Jörg
2020-10-26 16:23       ` Stefan Kangas
2020-10-26 19:57         ` Harald Jörg
2020-10-27  0:58           ` Stefan Kangas [this message]
2020-10-31 15:07     ` Philipp Stephani

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=CADwFkmmgqarCDi27E3Jnm4sbdUkmtGy3pwMw_uFkwg+j4JN+fg@mail.gmail.com \
    --to=stefan@marxist.se \
    --cc=emacs-devel@gnu.org \
    --cc=haj@posteo.de \
    --cc=monnier@iro.umontreal.ca \
    --cc=phst@google.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 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).