syntax highlighting in VSCode requires space between elm and open brace about litvis HOT 3 OPEN

Yes, that makes sense, for the reasons discussed.

from litvis.

Created remarkjs/remark#528 and prettier/prettier#9155 to see if we can fix this on the formatting front.

from litvis.

Hi Jo! WDYT of stopping the support of non-whitespace characters as the delimiter in litivs? See remarkjs/remark#528 (comment).

Doing so will include the removal of my hack in Prettier prettier/prettier#4783 as well as changing how mume separates the args from the language 'word'. This will make things in sync with how VSCode highlights the syntax.

I think that we initially got confused by what Atom was doing. If it only looked for spaces and tabs as word separators, we would do too. At the moment, it seems like we've ended up on a small island of not following the markdown specs.

from litvis.