unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Stefan Kangas <stefan@marxist.se>
To: Tim Landscheidt <tim@tim-landscheidt.de>
Cc: 29859@debbugs.gnu.org, Daniel Colascione <dan.colascione@gmail.com>
Subject: bug#29859: 25.3; MozRepl support is/will be no longer useful
Date: Mon, 10 Aug 2020 08:31:54 -0700	[thread overview]
Message-ID: <CADwFkm=wJiGKoFXY4FLq1XV5CYXcPudJPCZUUy0vvaF-R_F1SA@mail.gmail.com> (raw)
In-Reply-To: <87373xfgnx.fsf@passepartout.tim-landscheidt.de> (Tim Landscheidt's message of "Tue, 26 Dec 2017 19:11:30 +0000")

Tim Landscheidt <tim@tim-landscheidt.de> writes:

> Firefox 57 ("Quantum") removed the possibility to install
> extensions à la MozRepl
> (https://addons.mozilla.org/de/firefox/addon/mozrepl/).  To
> quote MozRepl's README.md (https://github.com/bard/mozrepl):
>
> | Important Notice
>
> | Key technologies upon which MozRepl depends will be retired
> | from the Mozilla platform in November 2017.  If you are re-
> | lying on MozRepl, please investigate migration paths.  The
> | last known compatible version is Firefox 54.
>
> | […]
>
> The current Firefox ESR release is based on Firefox 52 and
> should allow MozRepl to be installed until August 2018
> (https://www.mozilla.org/en-US/firefox/organizations/), but
> I did not test that.
>
> Thus the large code section in lisp/progmodes/js.el relating
> to MozRepl is unfortunately no longer useful and could be
> removed now or in September 2018 at the latest.  (Personal
> guess: Nobody is using Emacs with Firefox ESR, so removing
> it from the next release would not hurt anyone.)

So I guess we could mark this functionality as obsolete in Emacs 28.1.

Best regards,
Stefan Kangas





  parent reply	other threads:[~2020-08-10 15:31 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-12-26 19:11 bug#29859: 25.3; MozRepl support is/will be no longer useful Tim Landscheidt
2017-12-27 11:10 ` Charles A. Roelli
2017-12-27 16:15 ` Eli Zaretskii
2020-08-10 15:31 ` Stefan Kangas [this message]
2020-08-10 15:34   ` Dmitry Gutov
2020-08-12 13:10     ` Stefan Kangas
2020-08-12 13:15       ` Dmitry Gutov
2020-08-12 14:05         ` Phil Sainty
2020-08-12 14:13           ` Stefan Kangas
2020-08-12 14:28             ` Colin Baxter
2020-08-12 16:00               ` Stefan Kangas
2020-08-12 16:37                 ` Colin Baxter
2020-08-12 16:44                   ` Dmitry Gutov
2020-08-13  6:02                     ` Colin Baxter
2020-08-13  9:18                       ` Dmitry Gutov
2020-08-13  9:40                         ` Stefan Kangas
2020-08-13  9:42                           ` Dmitry Gutov
2020-08-12 14:33             ` Phil Sainty
2020-08-12 15:59               ` Stefan Kangas
2020-08-12 13:17       ` Lars Ingebrigtsen
2022-04-21 15:10 ` 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='CADwFkm=wJiGKoFXY4FLq1XV5CYXcPudJPCZUUy0vvaF-R_F1SA@mail.gmail.com' \
    --to=stefan@marxist.se \
    --cc=29859@debbugs.gnu.org \
    --cc=dan.colascione@gmail.com \
    --cc=tim@tim-landscheidt.de \
    /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).