From: Eli Zaretskii <eliz@gnu.org>
To: Yuan Fu <casouri@gmail.com>
Cc: jostein@kjonigsen.net, jostein@secure.kjonigsen.net,
theo@thornhill.no, 60546@debbugs.gnu.org
Subject: bug#60546: 29.0.60; typescript-ts-mode and tsx-ts-mode does not highlight variable-declarations in catch-clauses
Date: Fri, 06 Jan 2023 09:40:10 +0200 [thread overview]
Message-ID: <83zgawun51.fsf@gnu.org> (raw)
In-Reply-To: <22B8D169-C2FE-4CAA-8553-91692C4086CA@gmail.com> (message from Yuan Fu on Thu, 5 Jan 2023 23:09:06 -0700)
> Cc: jostein@kjonigsen.net, theo@thornhill.no, 60546@debbugs.gnu.org
> From: Yuan Fu <casouri@gmail.com>
> Date: Thu, 5 Jan 2023 23:09:06 -0700
>
> [...] release, which I guess is one or two month ahead (pure guess, I don’t really know)?
The first pretest version will hopefully be in a month or so. I don't
yet have a good idea about the release date of Emacs 29.1, which will
happen after we finish the pretest phase.
next prev parent reply other threads:[~2023-01-06 7:40 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-04 8:17 bug#60546: 29.0.60; typescript-ts-mode and tsx-ts-mode does not highlight variable-declarations in catch-clauses Jostein Kjønigsen
[not found] ` <handler.60546.B.16728202687178.ack@debbugs.gnu.org>
2023-01-04 9:30 ` bug#60546: Acknowledgement (29.0.60; typescript-ts-mode and tsx-ts-mode does not highlight variable-declarations in catch-clauses) Jostein Kjønigsen
2023-01-04 9:32 ` Jostein Kjønigsen
2023-01-04 9:58 ` Jostein Kjønigsen
2023-01-05 21:26 ` Jostein Kjønigsen
2023-01-06 6:09 ` bug#60546: 29.0.60; typescript-ts-mode and tsx-ts-mode does not highlight variable-declarations in catch-clauses Yuan Fu
2023-01-06 7:22 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-06 7:40 ` Eli Zaretskii [this message]
2023-01-08 2:20 ` Yuan Fu
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=83zgawun51.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=60546@debbugs.gnu.org \
--cc=casouri@gmail.com \
--cc=jostein@kjonigsen.net \
--cc=jostein@secure.kjonigsen.net \
--cc=theo@thornhill.no \
/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.