public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Jeremy Theler <jeremy-24em0bpozeFWk0Htik3J/w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: Re: adding new syntax highlighting xml in pandoc-1.19.2.1
Date: Thu, 22 Jun 2017 05:21:35 -0300	[thread overview]
Message-ID: <1498119695.2364.0.camel@seamplex.com> (raw)
In-Reply-To: <20170621115837.GA31670-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>

It seems I am in luck. It works like a charm!
Looking forward for the new version!

Thanks
--
jeremy theler
www.seamplex.com


On Wed, 2017-06-21 at 13:58 +0200, John MacFarlane wrote:
> You're in luck.  This gets much easier in the dev version of
> pandoc (to be released eventually as 2.0); you can just use
> a command line option --syntax-defintion=FILE.
> 
> You might try getting a binary from
> pandoc-extras/pandoc-nightly, but be aware that there are
> many other changes as well.
> 
> +++ Jeremy Theler [Jun 21 17 07:58 ]:
> > Hi all
> > 
> > I have been using the method described here
> > 
> > https://analyzethedatanotthedrivel.org/2012/09/20/pandoc-based-j-sy
> > ntax-highlighting/
> > 
> > to add my xml definitions to pandoc. But now pandoc switched to
> > skylighting
> > https://github.com/jgm/pandoc/releases/tag/1.19.2  and now I am
> >  having
> > a hard time getting the new pandoc to find and use my xml.
> > 
> > Any advice on how to re-compile pandoc with a customized xml syntax
> > highlighting file?
> > 
> > Thanks
> > --
> > jeremy theler
> > www.seamplex.com
> > 
> > -- 
> > You received this message because you are subscribed to the Google
> > Groups "pandoc-discuss" group.
> > To unsubscribe from this group and stop receiving emails from it,
> > send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> > To post to this group, send email to pandoc-discuss-/JYPxA39Uh4Ykp1iOSErHA@public.gmane.org
> > m.
> > To view this discussion on the web visit https://groups.google.com/
> > d/msgid/pandoc-discuss/1498042711.1710.2.camel%40seamplex.com.
> > For more options, visit https://groups.google.com/d/optout.
> 
> 

-- 
You received this message because you are subscribed to the Google Groups "pandoc-discuss" group.
To unsubscribe from this group and stop receiving emails from it, send an email to pandoc-discuss+unsubscribe-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/1498119695.2364.0.camel%40seamplex.com.
For more options, visit https://groups.google.com/d/optout.


      parent reply	other threads:[~2017-06-22  8:21 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-06-21 10:58 Jeremy Theler
     [not found] ` <1498042711.1710.2.camel-24em0bpozeFWk0Htik3J/w@public.gmane.org>
2017-06-21 11:58   ` John MacFarlane
     [not found]     ` <20170621115837.GA31670-BKjuZOBx5Kn2N3qrpRCZGbhGAdq7xJNKhPhL2mjWHbk@public.gmane.org>
2017-06-22  8:21       ` Jeremy Theler [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=1498119695.2364.0.camel@seamplex.com \
    --to=jeremy-24em0bpozefwk0htik3j/w@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).