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
Reported by: jostein <at> kjonigsen.net
Date: Tue, 29 Nov 2022 20:04:01 UTC
Severity: normal
Found in version 29.0.60
Done: Eli Zaretskii <eliz <at> gnu.org>
Bug is archived. No further changes may be made.
Full log
Message #71 received at 59691 <at> debbugs.gnu.org (full text, mbox):
[Message part 1 (text/plain, inline)]
Eli Zaretskii <eliz <at> gnu.org> writes:
>> 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
>> Date: Thu, 01 Dec 2022 09:12:58 +0100
>>
>> > Looks like some "git merge" snafu? You are in fact reverting a change I
>> > made in NEWS yesterday.
>> >
>>
>> You're right - I think I fixed it now.
>
> Yes, thanks.
>
>> > I don't see a change to auto-mode-alist to turn on each mode for the files
>> > it supports? I thought this was the idea? Or is this because we don't want
>> > tree-sitter based modes to be turned on by default? In that case, how do we
>> > explain to users that they should use each mode in the relevant cases?
>>
>> I think there should be
>>
>>
>> ;;;###autoload
>> (add-to-list 'auto-mode-alist '("\\.ts\\'" . typescript-ts-mode))
>>
>> ;;;###autoload
>> (add-to-list 'auto-mode-alist '("\\.tsx\\'" . tsx-ts-mode))
>
> Yes, I missed that, sorry. But the NEWS entry should clearly say that one
> mode is the default for *.ts files, the other for *.tsx files.
No worries :)
Is this patch suitable?
Theo
[0001-Add-new-TypeScript-mode-tsx-ts-mode.patch (text/x-diff, attachment)]
This bug report was last modified 2 years and 230 days ago.
Previous Next
GNU bug tracking system
Copyright (C) 1999 Darren O. Benham,
1997,2003 nCipher Corporation Ltd,
1994-97 Ian Jackson.