From: Lars Ingebrigtsen <larsi@gnus.org>
To: "Basil L. Contovounesios" <contovob@tcd.ie>
Cc: "andrés ramírez" <rrandresf@gmail.com>,
41745@debbugs.gnu.org, dgutov@yandex.ru
Subject: bug#41745: 28.0.50; problem with json file and which-function on pretest an master
Date: Sun, 20 Feb 2022 15:15:14 +0100 [thread overview]
Message-ID: <87a6elr5e5.fsf@gnus.org> (raw)
In-Reply-To: <87mu5epu6b.fsf@tcd.ie> (Basil L. Contovounesios's message of "Sun, 07 Jun 2020 20:11:56 +0100")
"Basil L. Contovounesios" <contovob@tcd.ie> writes:
> If it's not a syntax that js-mode officially supports, then the fact
> that it worked in 26.3 is just a happy coincidence, and not something
> that has to be maintained.
>
> Unless you or someone else can confirm that this is supported syntax, I
> don't see a bug here. The reason I'm not sure is because I'm not
> familiar with js-mode and the different flavours of JS-like syntax that
> are meant to be supported.
(I'm going through old bug reports that unfortunately weren't resolved
at the time.)
Skimming this bug report, it seems the conclusion is that this isn't a
bug, so I'm therefore closing this bug report.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
prev parent reply other threads:[~2022-02-20 14:15 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-06-07 4:12 bug#41745: 28.0.50; problem with json file and which-function on pretest an master Andrés Ramírez
2020-06-07 12:23 ` Basil L. Contovounesios
2020-06-07 13:49 ` Dmitry Gutov
2020-06-07 15:17 ` Basil L. Contovounesios
2020-06-07 16:53 ` andrés ramírez
2020-06-07 16:44 ` andrés ramírez
2020-06-07 18:17 ` Basil L. Contovounesios
2020-06-07 18:56 ` andrés ramírez
2020-06-07 19:11 ` Basil L. Contovounesios
2020-06-07 19:28 ` andrés ramírez
2020-06-07 20:34 ` Basil L. Contovounesios
2020-06-07 20:20 ` Dmitry Gutov
2020-06-07 20:34 ` Basil L. Contovounesios
2020-06-07 20:44 ` Dmitry Gutov
2022-02-20 14:15 ` Lars Ingebrigtsen [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
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=87a6elr5e5.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=41745@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--cc=dgutov@yandex.ru \
--cc=rrandresf@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 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).