[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#59691: Html-like constructs fail in typescript
From: |
Theodor Thornhill |
Subject: |
bug#59691: Html-like constructs fail in typescript |
Date: |
Wed, 30 Nov 2022 15:47:56 +0100 |
Eli Zaretskii <eliz@gnu.org> writes:
>> Date: Wed, 30 Nov 2022 14:00:49 +0100
>> From: Theodor Thornhill <theo@thornhill.no>
>> CC: 59691@debbugs.gnu.org, jostein@kjonigsen.net, casouri@gmail.com
>>
>>
>>
>> On 30 November 2022 13:35:49 CET, Eli Zaretskii <eliz@gnu.org> wrote:
>> >> From: Theodor Thornhill <theo@thornhill.no>
>> >> Cc: jostein@kjonigsen.net, casouri@gmail.com, eliz@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
bug#59691: Html-like constructs fail in typescript, Eli Zaretskii, 2022/11/30
bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Yuan Fu, 2022/11/30
- bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Eli Zaretskii, 2022/11/30
- bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Theodor Thornhill, 2022/11/30
- bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Eli Zaretskii, 2022/11/30
- bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Theodor Thornhill, 2022/11/30
- bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Eli Zaretskii, 2022/11/30
- bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Theodor Thornhill, 2022/11/30
- bug#59691: 29.0.60; typescript-ts-mode: any HTML-like elements causes fontification to become invalid and remaining parse-tree to become jsx-expression, Theodor Thornhill, 2022/11/30