public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Srini N <srini32904-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Help running pandoc/latex on simplest markdown file
Date: Mon, 13 Nov 2023 21:23:37 -0800 (PST)	[thread overview]
Message-ID: <3d175dc1-5e5f-46a2-8008-267a0f303c46n@googlegroups.com> (raw)


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

Step 1: Created simple *test.md *with just three lines below:

# Primary header (similar to HTML H1 tag)
## Secondary header (similar to HTML H2 tag)
### Tertiary header (similar to HTML H3 tag)

Step 2: Ran following command

docker run --rm --volume "$(pwd):/data" --user $(id -u):$(id -g) --platform 
*linux/amd64* *pandoc/latex* *test.md* -o *outfile.pdf*

And no file is generated and no error is thrown. Had to use "--platform 
linux/amd64" option because default option does not work on Apple Mac with 
M1 chip. No idea what is wrong.

Appreciate any help

Thanks much

-- 
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/3d175dc1-5e5f-46a2-8008-267a0f303c46n%40googlegroups.com.

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

             reply	other threads:[~2023-11-14  5:23 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-11-14  5:23 Srini N [this message]
     [not found] ` <3d175dc1-5e5f-46a2-8008-267a0f303c46n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2023-12-05 15:35   ` Julien Dutant

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=3d175dc1-5e5f-46a2-8008-267a0f303c46n@googlegroups.com \
    --to=srini32904-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).