[infinispan-dev] code highlight in github/asciidoc

Manik Surtani manik at infinispan.org
Wed Oct 30 12:49:24 EDT 2013


I only suggested AsciiDoc to be consistent with the markup used for our
documentation.  Having two different markup syntaxes in use for the project
could get annoying... but yes, I agree that the lack of syntax highlighting
on the wiki can be even more annoying.


On 30 October 2013 12:55, Mircea Markus <mmarkus at redhat.com> wrote:

> Github's wiki asciidoc doesn't play nicely with syntax highlighting:
> displays all the code with the same plain color, instead of highlighting
> the syntax elements like the IDEs do.
> E.g. the sample code provided in the wiki asciidoc help:
>
> .python.py
> [source,python]
> ----
> # i just wrote a comment in python
> print "something"
> # and maybe one more
> ----
>
> renders like:
> http://screencast.com/t/k6JVQrWQ4
>
> Whilst the markdown equivalent:
>
> ```python
> # i just wrote a comment in python
> print "something"
> # and maybe one more
> ```
>
> renders as expected:
> http://screencast.com/t/YLMhs31Jm
>
> I think this has been a problem for quite a while now:
> https://github.com/gollum/gollum/issues/280
> Does anyone see any problem with allowing both markdown and asciidoc
> editors for our wiki? They both have pretty basic syntax and markdown seems
> to be better integrated (I guess that's why it's also the default editor).
>
>
> Cheers,
> --
> Mircea Markus
> Infinispan lead (www.infinispan.org)
>
>
>
>
>
> _______________________________________________
> infinispan-dev mailing list
> infinispan-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/infinispan-dev
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/infinispan-dev/attachments/20131030/7b5f0a12/attachment.html 


More information about the infinispan-dev mailing list