Fork me on GitHub
#calva
<
2022-01-19
>
Cora (she/her)04:01:34

time to give calva another shot

Cora (she/her)04:01:40

well this is odd

Cora (she/her)04:01:42

The character U+a789 "꞉" could be confused with the character U+003a ":", which is more common in source code.

Cora (she/her)04:01:52

the characters with boxes around them are the suspicious characters

Cora (she/her)04:01:31

the highlighted spaces say The character U+00a0 is invisible.

Cora (she/her)04:01:05

which comes from this setting

Tero Matinlassi05:01:59

@corasaurus-hex I think there’s an issue in GitHub about this: https://github.com/BetterThanTomorrow/calva/issues/1475 (the use of those characters is intentional, iirc)

Cora (she/her)05:01:34

I didn't search well enough, I guess 😅

Tomas Brejla19:01:26

I think you can right-click that specific rendered box around : or space and if I remember correctly, there's a context option to disable rendering of that box for that specific character.

Cora (she/her)19:01:19

right, I just don't want those characters ignored in general

pez20:01:59

This will happen with the next Calva update anyway. Even if scoped to [clojure]. https://github.com/BetterThanTomorrow/calva/pull/1485

orestis06:01:03

What is the rationale for using those characters anyway, @U0ETXRFEW?

pez08:01:05

The space-ish character because when we used a regular space, it got ugly for people who had trailing whitespace highlighting on. The colon-ish one is because it was an easy way to syntax highlight the different components of the prompt.

orestis08:01:26

ah, gotcha