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: Convert output from "colordiff" to "markdown", (file_with_ansi_colors ---> markdown)
Date: Tue, 28 Apr 2020 07:09:22 -0300	[thread overview]
Message-ID: <7097185ebdccd3eeb1fde8f23f9bb3fb92a1e1bf.camel@seamplex.com> (raw)
In-Reply-To: <df16b3b3-aaf0-4f9c-b7ae-8df24a3f027b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

Hi Raimundo

Try passing this xml file
https://github.com/KDE/syntax-highlighting/blob/master/data/syntax/diff.xml
as --syntax-definition=diff.xml to pandoc


Regards
--
jeremy theler
www.seamplex.com



On Tue, 2020-04-28 at 02:38 -0700, Raimundo Carlos Collado wrote:
> Hello
> 
> Any suggestion for this?
> 
> $ colordiff file1 file2 > output_ansi_colors
> $ cat output_ansi_colors 
> (view in a terminal the colors for the escape sequences)
> 
> ??? its possible convert with pandoc, "output_ansi_colors" to
> "markdown"??
> 
> 
> Many thanks
> -- 
> 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 view this discussion on the web visit 
> https://groups.google.com/d/msgid/pandoc-discuss/df16b3b3-aaf0-4f9c-b7ae-8df24a3f027b%40googlegroups.com
> .


      parent reply	other threads:[~2020-04-28 10:09 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-04-28  9:38 Raimundo Carlos Collado
     [not found] ` <df16b3b3-aaf0-4f9c-b7ae-8df24a3f027b-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-04-28 10:09   ` 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=7097185ebdccd3eeb1fde8f23f9bb3fb92a1e1bf.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).