public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: 'John Sampson' via pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc does nothing when converting file from markdown to latex
Date: Thu, 09 Dec 2021 08:19:37 -0800	[thread overview]
Message-ID: <m25yrxeoo6.fsf@Johns-Air.hsd1.ca.comcast.net> (raw)
In-Reply-To: <e1c7427c-732f-4120-ae8e-8d7500799b66n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


Do you get the prompt again on the next line? If so, that's
the expected behavior. Pandoc won't print anything to indicate
that it has succeeded, but you should now see the file
outfile.tex in your directory.

(By the way, myfile.md should be in your current working
directory -- it doesn't matter if it's in the same directory
containing pandoc.exe.)

"'John Sampson' via pandoc-discuss"
<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org> writes:

> I typed the command "pandoc myfile.md -f markdown -t latex -s -o 
> outfile.tex"
> where myfile.md is in the same directory as pandoc,exe but nothing 
> happened. When I pressed "return" the caret went to the next line and 
> stayed there. I am new to pandoc - what am I doing wrong?
>
> -- 
> 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/e1c7427c-732f-4120-ae8e-8d7500799b66n%40googlegroups.com.


  parent reply	other threads:[~2021-12-09 16:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-08 12:40 'John Sampson' via pandoc-discuss
     [not found] ` <e1c7427c-732f-4120-ae8e-8d7500799b66n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-09  0:54   ` Gregory Weber
2021-12-09 12:10   ` Sébastien Boisgérault
2021-12-09 16:19   ` John MacFarlane [this message]
     [not found]     ` <m25yrxeoo6.fsf-d8241O7hbXoP5tpWdHSM3tPlBySK3R6THiGdP5j34PU@public.gmane.org>
2021-12-09 17:16       ` 'John Sampson' via pandoc-discuss
     [not found]         ` <5a2f6e40-1678-41e7-a486-1e9ac0da0317n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2021-12-09 17:27           ` 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=m25yrxeoo6.fsf@Johns-Air.hsd1.ca.comcast.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@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).