public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Mirjalol Norqulov <mirjalol2401-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc output to stdout
Date: Wed, 19 Jul 2017 10:26:29 -0700 (PDT)	[thread overview]
Message-ID: <b2bbef60-8140-41e9-bba9-a80f84bb776c@googlegroups.com> (raw)
In-Reply-To: <CALwjjMiABu3rX8P=kNic4B-n-yXLC-XtuSLCguvcr2p_kTHmKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 919 bytes --]

I'm converting to docx, it seems pandoc can not write docx output to 
stdout. Any ideas?

среда, 19 июля 2017 г., 16:43:08 UTC+5 пользователь John O'Regan написал:
>
> Hi Mirjalol, 
>
> If you don't specify an output file on the command line, Pandoc will 
> write to STDOUT by default. 
>
> John 
>

-- 
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/b2bbef60-8140-41e9-bba9-a80f84bb776c%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[-- Attachment #1.2: Type: text/html, Size: 1470 bytes --]

  parent reply	other threads:[~2017-07-19 17:26 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-07-19 10:56 Mirjalol Norqulov
     [not found] ` <3e6f4efa-c3d5-4fd0-8692-38ecd6484ad8-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-19 11:43   ` John O'Regan
     [not found]     ` <CALwjjMiABu3rX8P=kNic4B-n-yXLC-XtuSLCguvcr2p_kTHmKQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-19 17:13       ` Mirjalol Norqulov
2017-07-19 17:26       ` Mirjalol Norqulov [this message]
     [not found]         ` <b2bbef60-8140-41e9-bba9-a80f84bb776c-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-19 18:06           ` John O'Regan
     [not found]             ` <CALwjjMjQDADwEYGPoM0mHqtdauQPKadgEJ4xuW=DDsAdLovTYg-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2017-07-20  2:52               ` Mirjalol Norqulov
     [not found]                 ` <f824b8a8-acef-4d19-9d88-f302b1681172-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2017-07-20  5:11                   ` Ivan Lazar Miljenovic
2017-07-21 21:24                   ` Kolen Cheung
2017-07-19 21:09           ` Albert Krewinkel
2017-07-23  8:02           ` John MacFarlane

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=b2bbef60-8140-41e9-bba9-a80f84bb776c@googlegroups.com \
    --to=mirjalol2401-re5jqeeqqe8avxtiumwx3w@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).