💾 Archived View for rawtext.club › ~sloum › geminilist › 000630.gmi captured on 2020-10-31 at 01:42:49. Gemini links have been rewritten to link to archived content
⬅️ Previous capture (2020-09-24)
-=-=-=-=-=-=-
Felix Queißner felix at masterq32.de
Thu May 14 20:57:42 BST 2020
- - - - - - - - - - - - - - - - - - - ``` Hey, > There's an existing convention in Markdown, if I'm not mistaken, of > mentioning a programming language's name in curly brackets after an > opening code fence, which is used as a hint for syntax highlighting. > I'm not clear on the details, entirely, but people have mentioned it > before.Yeah, there kinda is [0]. It's called the "info string" and has (byspec) no defined meaning, it's usually used to hint the syntaxhighlighter on the correct programming language. > It might be smart to adopt/extend that syntax?I think that would be a good thing. I enjoyed some of the ASCII art youan find in gemini space and it would be nice to recognize these in asearch engine and filter these out. It could also allow to search forcertain programming languages (considering ascii art a PL) > For now I am leaning toward "recommended convention"...Yeah, sounds reasonable. Having the info string in the spec is a goodidea though, but make it's content not fixed Regardsxq [0] https://spec.commonmark.org/0.29/#fenced-code-blocks