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 #38 received at 59691 <at> debbugs.gnu.org (full text, mbox):

From: Theodor Thornhill <theo <at> thornhill.no>
To: Eli Zaretskii <eliz <at> gnu.org>
Cc: 59691 <at> debbugs.gnu.org, casouri <at> gmail.com, jostein <at> kjonigsen.net
Subject: Re: Html-like constructs fail in typescript
Date: Wed, 30 Nov 2022 15:47:56 +0100

Eli Zaretskii <eliz <at> gnu.org> writes:

>> Date: Wed, 30 Nov 2022 14:00:49 +0100
>> From: Theodor Thornhill <theo <at> thornhill.no>
>> CC: 59691 <at> debbugs.gnu.org, jostein <at> kjonigsen.net, casouri <at> gmail.com
>> 
>> 
>> 
>> On 30 November 2022 13:35:49 CET, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> >> From: Theodor Thornhill <theo <at> thornhill.no>
>> >> Cc: jostein <at> kjonigsen.net, casouri <at> gmail.com, eliz <at> gnu.org
>> >> Date: Tue, 29 Nov 2022 22:01:01 +0100
>> >> 
>> >> The solution is to create two modes: typescript-ts-mode and
>> >> tsx-ts-mode. They have separate parsers, and should be treated as
>> >> separate languages.  That means that in a .ts file we enable the
>> >> 'typescript' language, and in .tsx we enable the 'tsx' language.  This
>> >> exact issue is why they have two languages.
>> >
>> >This means the script posted by Yuan, which only creates a single grammar
>> >library for Typescript (the one for tsx), should be changed to instead
>> >produce two libraries, right?
>> 
>> Yes, I can fix that when the two modes are in :)
>
> Thanks.  But now I hear that the original analysis could be incomplete, and
> there actually is no problem, according to Jostein's last messages?

I don't think I agree with him. There are other constructs such as
generics that also can cause these ambiguities, IIRC

Theo

Previous Next

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