Windows Terminal does not treat U+2063 as an invisible character

[chromatic-aberration]

U+2063 ( Invisible Comma = "⁣" ) used in comments is not being treated as an invisible character in Windows Terminal. This seems to be unrelated to the picked font either (or the -n flag).
This results in following behaviour:

I am aware this is an issue on the side of Windows Terminal, but it seems like they have had similar unicode characters not being invisible as intended issues already reported a while ago with no sign of progress on fix on their side as of yet, so maybe here some alternate character or a flag could be implemented?

This behaviour was observed on circumflex v3.7 and windows terminal v1.20.11781.0

[bensadeh]

Hi @chromatic-aberration !

Thanks for using clx and thanks for letting me know about this.

It does indeed seem like a bug in the windows terminal, but that doesn't mean we can't find a good workaround.

Just some context: we use this symbol to collapse/expand the comment section from within less. Using h or k, we can filter out these special characters in real time, giving the impression that we expand or collapse the comments.

I think for this case, we can just find a suitable replacement unicode character that is invisible in both windows and unix/mac.

There need to be changes in two places:

• In the unicode constant here:

  circumflex/constants/unicode/unicode.go

  Line 5 in 7ff70f5

  InvisibleCharacterForExpansion = "⁣"

• In the lesskey file here:

  circumflex/less/lesskey

  Lines 6 to 10 in 7ff70f5

  	h filter ^M&!⁣\r
  	\kl filter ^M&!⁣\r
  	l filter ^M&!‌\r
  	\kr filter ^M&!‌\r

If you're able to find a good replacement unicode character, I'd be happy to receive a PR so that I can again test the changes on the mac side of things.