You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 4, 2024. It is now read-only.
@ReedCopsey, I'd suggest we use explicit languages everywhere as if it was github (we need the list, and it would be great if it was compatible with github flavor until we get our own "run live docs locally").
This will be easier to correct later if that's not the correct approach, and it seems the most effective.
In my changes, I assumed fsharp would be default but I'd actually prefer to be explicit everywhere (and to have a triple backtick key on my keyboard).
I'm fine with that. The problem is more when there isn't a language. It
doesn't seem to infer f#, but it's still doing _something_.
Does anyone know what would happen if we put am unknown language? I'd
actually like to do "output" or something... could be useful later for
styling if it's ignored now.
In my last PR, I moved a lot of "output" results into code blocks (which matched some portions of the code), but the formatter highlights them.
Is there a way to force it to not syntax highlight? My understanding, from every markdown tutorial, is that using triple back ticks without a language won't format, but that's not the case. For example, see the output here: https://msdn.microsoft.com/en-us/visualfsharpdocs/conceptual/arrays-%5Bfsharp%5D#searching-arrays
Note that "is" and "and" are getting highlighted blue.
Is there a language tag that will kill all highlighting?
The text was updated successfully, but these errors were encountered: