Never mind the other thread. I'd like to try and debug why asciidoc, invoked via the asciidocapi, is failing on this machine and not the other. Can someone point me to the part of the code where asciidoc will recognise the -a source-highlighter=pygments flag, and the part where it goes to use pygments instead of source-highlight?
On 30 October 2014 11:17, Harry Percival <[email protected]> wrote: > Progress! I've now got the asciidoc command-line working on both machines > ( the broken one has had an OS upgrade, although I didn't touch asciidoc, > and i'm still using the same virtualenv. baffling). But I still have > problems when going through the asciidoc API. Will follow up in another > thread. > > On 25 October 2014 22:03, <[email protected]> wrote: > >> Nope, sorry if that wasn't clear, it's the same version of pygments on >> both, 1.6... >> >> -- >> Sent from a mobile, excuse brevity. >> Harry Percival >> @hjwp >> +44 78877 02511 >> Original Message >> From: Lex Trotman >> Sent: Saturday, 25 October 2014 20:11 >> To: [email protected] >> Reply To: [email protected] >> Subject: Re: pygments highlighter works on one machine but not another? >> >> Has one machine got an old version of pygments that doesn't support >> gherkin?? >> >> Cheers >> Lex >> >> On 25 October 2014 22:10, Harry Percival <[email protected]> >> wrote: >> > Related to my last post -- I'm using pygments for my source >> highlighting. >> > Any idea why it would be working on one machine and not on another? >> > >> > cd /tmp >> > wget >> > >> https://raw.githubusercontent.com/hjwp/pelican-plugins/master/asciidoc_reader/test_data/article_for_pygments_highlighting.asc >> > asciidoc article_for_pygments_highlighting.asc >> > # shows errors with "source-highlight: could not find a language >> definition >> > for gherkin" etc >> > asciidoc -a source-highlighter=pygments >> > article_for_pygments_highlighting.asc >> > # works on one machine but not on another. >> > >> > On both machines, pygments is installed, pygmentize -v gives me version >> 1.6, >> > and I've tried it both in and out of virtualenvs... Any other ideas on >> why >> > it might not work in one case? Thoughts on what I should look into for >> > debugging? >> > >> > >> > >> > >> > >> > >> > -- >> > ------------------------------ >> > Harry J.W. Percival >> > ------------------------------ >> > Twitter: @hjwp >> > Mobile: +44 (0) 78877 02511 >> > Skype: harry.percival >> > >> > -- >> > You received this message because you are subscribed to the Google >> Groups >> > "asciidoc" group. >> > To unsubscribe from this group and stop receiving emails from it, send >> an >> > email to [email protected]. >> > To post to this group, send email to [email protected]. >> > Visit this group at http://groups.google.com/group/asciidoc. >> > For more options, visit https://groups.google.com/d/optout. >> >> -- >> You received this message because you are subscribed to the Google Groups >> "asciidoc" group. >> To unsubscribe from this group and stop receiving emails from it, send an >> email to [email protected]. >> To post to this group, send email to [email protected]. >> Visit this group at http://groups.google.com/group/asciidoc. >> For more options, visit https://groups.google.com/d/optout. >> > > > > -- > ------------------------------ > Harry J.W. Percival > ------------------------------ > Twitter: @hjwp > Mobile: +44 (0) 78877 02511 > Skype: harry.percival > -- ------------------------------ Harry J.W. Percival ------------------------------ Twitter: @hjwp Mobile: +44 (0) 78877 02511 Skype: harry.percival -- You received this message because you are subscribed to the Google Groups "asciidoc" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/asciidoc. For more options, visit https://groups.google.com/d/optout.
