From: Mike Crowe <drmikecrowe-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Markdown->Latex and Inline Links referencing included subdirectory files
Date: Wed, 26 Jun 2019 17:52:18 -0700 (PDT) [thread overview]
Message-ID: <f119fa7f-1cd2-4494-9e0d-88a417a269cc@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1690 bytes --]
Hey folks,
So, I'm building a PDF from bunch of markdown files. Starting at the top
file, I build a list of all the files references in a link, such as [Some
Topic](file1.md), [Another Topic](file2.md). My list would then contain:
README.md
file1.md
file2.md
etc.
However, I have subdirectories of markdown files, so my list of files is
more like:
README.md
file1.md
file2.md
topic1/file3.md
topic1/file4.md
topic2/file5.md
topic2/file6.md
To build the PDF, I'm essentially calling pandoc as follows:
pandoc --template templates/mytemplate.latex --listings --file-scope
--self-contained \
-f gfm \
-s $(cat files.lis) \
-o $OUTPUT.pdf
Overall, this is working great for all the markdown files in the root
directory (so file1.md, file2.md). However, all the markdown files in a
subdirectory (such as topic1/file3) show up as a link in the PDF, rather
than an inline link, and try to open up topic1/file3.md rather than jump to
the anchor.
As an aside, it *appears* that pandoc is creating the anchor for
topic1/file3.md as file3, though I'd prefer it were topic1file3.
--
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/f119fa7f-1cd2-4494-9e0d-88a417a269cc%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.
[-- Attachment #1.2: Type: text/html, Size: 2542 bytes --]
next reply other threads:[~2019-06-27 0:52 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-06-27 0:52 Mike Crowe [this message]
[not found] ` <f119fa7f-1cd2-4494-9e0d-88a417a269cc-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2019-06-28 8:59 ` mb21
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=f119fa7f-1cd2-4494-9e0d-88a417a269cc@googlegroups.com \
--to=drmikecrowe-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).