From: Yuan Fu <casouri@gmail.com>
To: Theodor Thornhill <theo@thornhill.no>
Cc: 60376@debbugs.gnu.org, eliz@gnu.org, jostein@kjonigsen.net
Subject: bug#60376: 29.0.60; Standardize csharp-ts-mode's font-lock features
Date: Sun, 1 Jan 2023 16:12:24 -0800 [thread overview]
Message-ID: <0D5F2396-277A-4017-AE0B-371F591BD141@gmail.com> (raw)
In-Reply-To: <7A5618C7-25D7-4B52-8D16-5C54F09FA4CA@gmail.com>
Theodor Thornhill <theo@thornhill.no> writes:
> Jostein Kjønigsen <jostein@secure.kjonigsen.net> writes:
>
>> On 01.01.2023 18:24, Jostein Kjønigsen wrote:
>>> Disregard previous patch.
>>>
>>> Consider instead please the patch attached to this email.
>>>
>>> It does 3 things all in one:
>>>
>>> * moves function-call fontification to level 4 only (in its own feature)
>>>
>>> * cleans up long-standing issues with "messy" rules for
>>> function-invocations. Removes the needs for "overrides".
>>>
>>> * also fixes issue with fonctification of self/this-method invocations.
>>>
>>> Theo: Can you try this patch and see what you think?
>>>
>>> --
>>>
>>> Jostein
>>
>> Disregard again (and sorry for the noise!)
>>
>> I've now gone through several files, done quite a bit of testing myself,
>> and found another few issues needing to be solved:
>>
>> * Inconsistent variable-name fontification (sometimes when used,
>> sometimes when declared, sometimes not when used, sometimes not when
>> declared)
>> * Variable declaration with explicit generic types
>> * new() expression fontification for generic types.
>> * Bleeding type-face into brackets for generic return-types in method
>> definitions
>> * Types when casting through as-expressions are not fontified at all.
>> * And more?
>>
>> I've solved those and combined all this into this latest patch, which
>> also moves function-invocation into its own (level 4) feature.
>>
>> This patch should be well beyond the "85%" which Eli has requested for
>> Emacs-29 :)
>>
>> *Theo:* Could you give this a test-spin, and I promise to call it a day? :)
>>
>
> Hi!
>
> No worries at all, I'm just glad you found some inspiration :-)
>
> This looks good to me. I think we are are all set - there are at least
> no more features needed. I guess we can still add some tweaks to the
> highlighting itself before the release?
>
> Yuan - you're next ;)
>
> Theo
Fantastic! I applied the patch, thanks!
Yuan
next prev parent reply other threads:[~2023-01-02 0:12 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-28 8:25 bug#60376: 29.0.60; Standardize csharp-ts-mode's font-lock features Yuan Fu
2022-12-29 19:55 ` Yuan Fu
2022-12-29 21:03 ` Jostein Kjønigsen
2022-12-30 8:21 ` Eli Zaretskii
2022-12-29 22:16 ` Yuan Fu
2022-12-30 8:19 ` Eli Zaretskii
2022-12-30 13:35 ` Jostein Kjønigsen
2022-12-30 14:15 ` Eli Zaretskii
2022-12-30 14:39 ` Jostein Kjønigsen
2022-12-30 15:39 ` Eli Zaretskii
2022-12-30 17:35 ` Jostein Kjønigsen
2022-12-30 19:30 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-31 9:53 ` Jostein Kjønigsen
2022-12-31 10:32 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-30 14:40 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2022-12-30 15:04 ` Jostein Kjønigsen
2022-12-31 22:21 ` Yuan Fu
2023-01-01 16:29 ` Jostein Kjønigsen
2023-01-01 17:24 ` Jostein Kjønigsen
2023-01-01 18:14 ` Jostein Kjønigsen
2023-01-01 18:41 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-02 0:12 ` Yuan Fu [this message]
2023-01-02 9:59 ` Jostein Kjønigsen
2023-01-03 5:43 ` Jostein Kjønigsen
2023-01-05 21:27 ` Jostein Kjønigsen
2023-01-03 6:51 ` Yuan Fu
2023-01-03 7:20 ` Theodor Thornhill via Bug reports for GNU Emacs, the Swiss army knife of text editors
2023-01-06 5:55 ` Yuan Fu
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=0D5F2396-277A-4017-AE0B-371F591BD141@gmail.com \
--to=casouri@gmail.com \
--cc=60376@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=jostein@kjonigsen.net \
--cc=theo@thornhill.no \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).