Closed asimenio-asteri closed 3 years ago
/=/
would be a problem in regexps. I’ll think about \=/
. Thanks!
thank you agin!
Well, IK i am against most people's thoughts here, but a) A regex which searches for '=' is actually a single token in my mind b) Editors like VSCode (and all tmLanguage-based ones, AFAIK) separate in tokens, and two different tokens can't ligate. In most langauges, regexes are matched with
regex:
name: constant.regexp.language
begin: /
end: (?<!\)/
captures:
0:
name: operator.regexp.language
or similarly with a before
/end
which tokenizes begin
, end
and the things between as three different tokens.
if it would be a problem w/ regexp, it could be a stylistic set?
There’re only 20 stylistic sets, and I would like to spend them on stuff that many people disagree about. I don’t have them all planned out, but that’s the idea. More votes → more chances for a stylistic set
so there will be a maximum of 20? if so, i don't think this should be one of them then
wait, there are 20 ss + 20 character variations, right?
There are 100 character variations, but they usually alter single characters :)
yes, what i meant is that by using cvs you free up a lot of ss.
I am a programmer and a chemistry. I use SMILES and I would like these ligatures. sidenote: /=/ is trans and \=/ cis. It is okay if you do not add these, they aren't really programming/maybe they conflict