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

View this message in rfc822 format

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> secure.kjonigsen.net, jostein <at> kjonigsen.net
Subject: 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
Date: Wed, 30 Nov 2022 19:21:58 +0100

On 30 November 2022 19:19:04 CET, Eli Zaretskii <eliz <at> gnu.org> wrote:
>> Date: Wed, 30 Nov 2022 19:10:04 +0100
>> From: Theodor Thornhill <theo <at> thornhill.no>
>> CC: casouri <at> gmail.com, jostein <at> secure.kjonigsen.net, 59691 <at> debbugs.gnu.org,
>>  jostein <at> kjonigsen.net
>> 
>> >Our automatic turning-on of major-modes looks at the file-name extension and
>> >little else (magic-mode-alist is not useful here).  So if a file whose
>> >extension is XYZ can have more than one applicable major-mode, we should try
>> >to do something to turn on the correct mode automatically.  What can we do?
>> 
>> We are lucky because the extensions in question are ts, tsx and js. So we don't need any smartness :)
>
>And the extensions always say unequivocally what mode to use?  Then yes, we
>are lucky, and need just one more major mode (and one more grammar library).

I have already made that commit, but it is waiting on the  indent style patch :)

Previous Next

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