Firacode: Ligature Request: /**

[joshfriend]

Swift uses /** to start a documentation comment block. There are currently ligatures for /* and */ and it looks odd when combined with /**.

[jkuchar]

Same for PHP :) 👍

[mseymour]

And CSS.

[xgouchet]

Same for Javadoc :+1:

[dhouck]

A lot of documentation conventions use it, including the above and Doxygen.

This used to exist (see #219) but was removed because it was misaligned. I think the proper solution is to add it back, properly aligned.

[dhouck]

Other useful sequences for Doxygen comments are ///, /*!, //!, and each of the four suggested markers followed by <. I think /// is also used for C#, but I don’t know if the others will be generally useful. Personally, I use /**, ///, and ///<.

[Snowman-25]

How about having the /** display like /: but have the dots replaced with asterisks? It wouldn't be too long then.

[tonsky]

There used to be /** but it was removed due to conflict with file paths and bad alignement with multiline commets block. See #219 and #238. If you have ideas how those could be avoided I’ll be happy to bring it back

[Snowman-25]

Well, for docs, the line with /* typically doesn't have text, so only having the /* ligature if there's a linebreak or newline character after it should work fine (if possible) and not affect the other cases you mentioned

[tonsky]

Still, what do you think could be improved? The more I work with Fira Code, the more I think it’s not worth it having ligatures for simple/trivial cases like this. They look pretty good as they are, and there’s a lot of complexity bringing them around for a really small gain.

[joshfriend]

removed due to conflict with file paths

Thats a really good point. Making doc comment blocks look a little bit nicer is not worth having awful looking glob patterns...