On Wed, Aug 30, 2017 at 7:05 AM, <fossil-users-requ...@lists.fossil-scm.org>
wrote:
>
> Date: Tue, 29 Aug 2017 22:55:56 -0500
> From: Andy Goth <andrew.m.g...@gmail.com>
> To: fossil-users@lists.fossil-scm.org
> Subject: Re: [fossil-users] toc.tcl
> Message-ID: <56c8452e-5530-7c0d-c077-fa2b35375...@gmail.com>
> Content-Type: text/plain; charset=utf-8; format=flowed
>
> dewey.hylton says "```" imbues syntax highlighting whereas indented
> lines are left plain.  Fossil doesn't do any kind of syntax highlighting
> at this point.  Is there any interest in having this feature?  I feel
> syntax highlighting is both expected and bloat.  We would have to decide
> which we prefer: being simple or having me-too features.
>
> I'm curious how the Markdown formatter would know what language rules to
> use for syntax highlighting, so surely there's more to the syntax than
> bracketing ("fencing") the code with lines consisting entirely of "```".
> I searched online and found the answer to be: put the name of the syntax
> highlight mode (i.e. the language) right after the first "```" on the
> same line, for instance "```ruby".
>

There are JavaScript scripts to do syntax highlighting in the browser, so
anyone who wanted to do that could. Hopefully, there is one that looks for
something like a <div class="syntaxhl" lang="lang"> element. then
libdiscount could be enhanced to enclose code-fenced code in that element.

I am neutral on whether to do it, but this seems like it could be done with
a few small changes.
_______________________________________________
fossil-users mailing list
fossil-users@lists.fossil-scm.org
http://lists.fossil-scm.org:8080/cgi-bin/mailman/listinfo/fossil-users

Reply via email to