GNU bug report logs - #59691
29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression

Previous Next

Full log

Message #14 received at 59691 <at> debbugs.gnu.org (full text, mbox):

From: Theodor Thornhill <theo <at> thornhill.no>
To: Jostein Kjønigsen <jostein <at> secure.kjonigsen.net>
Cc: 59691 <at> debbugs.gnu.org, casouri <at> gmail.com, jostein <at> kjonigsen.net,
 eliz <at> gnu.org
Subject: Re: Html-like constructs fail in typescript
Date: Tue, 29 Nov 2022 22:47:38 +0100

On 29 November 2022 22:37:25 CET, "Jostein Kjønigsen" <jostein <at> secure.kjonigsen.net> wrote:
>Nice!
>
>Should we until further notice assume that js-ts-mode suffers from the same issues, and that a jsx-ts-mode might be needed too? To me it at least sounds plausible. 

No, because there are no ambiguities in the grammar with types and jsx.

>
>Speaking of duplication… Now that we have tree-sitter wouldn’t it be possible to use the same parser and/or the same major-modes for JS/JSX as we already do for TS/TSX? JS/JSX is just Typescript without the type-annotations, right?
>
>Or are there good reasons for having separate modes for these?
>

Not sure. I like that a mode maps to a tree-sitter grammar, and personally I don't want to intertwine things to early.

>

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.