public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Wasif Hasan Baig
	<pr.wasif-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Runing Pandoc as a document tranformation server?
Date: Sun, 12 Dec 2021 18:16:10 -0800	[thread overview]
Message-ID: <m2wnk99rmd.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <08377700-0bac-478b-8e7d-65adededb7d7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Not sure what you mean.    Run without arguments, pandoc will
consume input from stdin and pass output to stdout; however, it
will not produce any output until it has consumed the entire
input, so this may not be what you have in mind.

Or you may be thinking of something like
https://github.com/jgm/pandoc-server

Wasif Hasan Baig <pr.wasif-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> writes:

> Is it possible to run Pandoc as document transformation server that works 
> on an input stream?
>
> -- 
> 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/08377700-0bac-478b-8e7d-65adededb7d7n%40googlegroups.com.


      parent reply	other threads:[~2021-12-13  2:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-13  1:42 Wasif Hasan Baig
     [not found] ` <08377700-0bac-478b-8e7d-65adededb7d7n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-13  2:16   ` John MacFarlane [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=m2wnk99rmd.fsf@Johns-Air.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org \
    --cc=pr.wasif-Re5JQEeQqe8AvxtiuMwx3w@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).