public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: John MacFarlane <jgm-TVLZxgkOlNX2fBVCVOL8/A@public.gmane.org>
To: Joseph Reagle
	<joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>,
	pandoc-discuss
	<pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: tip for paths that work locally and served?
Date: Wed, 02 Jun 2021 10:44:26 -0600	[thread overview]
Message-ID: <m2r1hkusgl.fsf@johnmacfarlane.net> (raw)
In-Reply-To: <f35add93-e541-094c-6c13-feaa5410115e-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>


It's a markdown syntax extension, so no, it doesn't affect
command line options, only the body text.

Joseph Reagle <joseph.2011-T1oY19WcHSwdnm+yROfE0A@public.gmane.org> writes:

> Thinking about this a bit more, `rebase_relative_paths` doesn't affect the `-c` parameter. Should it? Right now it's limited to links/images appearing within the markdown files themselves, but if I were to use something like:
>
> 	pandoc chap*/*.md -f markdown+rebase_relative_paths
> 	-c ../styles/base.css
>
> It might be useful -- or I might expect -- the resulting link tags to be
>
> 	<link rel="stylesheet" href="../../style/base.css" />
>
> *If* that were the case, and then pandoc was willing to interpret `~` in file parameters as a relative link and rebase them, then my issue would be solved.
>
> I'm not convinced that's a great idea, only that it is an idea. 😉 Otherwise, what I should do is modify my python build scripts to create a custom `-c` parameter for each markdown file built using the working directory `relative_to` the location of the markdown file [1].
>
> [1]: https://docs.python.org/3/library/pathlib.html#pathlib.PurePath.relative_to
>
> -- 
> 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/f35add93-e541-094c-6c13-feaa5410115e%40reagle.org.

-- 
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/m2r1hkusgl.fsf%40johnmacfarlane.net.


  parent reply	other threads:[~2021-06-02 16:44 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-06-01 15:08 Joseph Reagle
     [not found] ` <70fc8d18-e32d-1468-c860-3ec9005f4a00-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-01 21:42   ` Joseph Reagle
     [not found]     ` <f35add93-e541-094c-6c13-feaa5410115e-T1oY19WcHSwdnm+yROfE0A@public.gmane.org>
2021-06-02 11:08       ` BPJ
     [not found]         ` <CADAJKhAg8V4_++1oeJvja=RQgZfbk3nOX--vwKxRbw0+emYctw-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-06-02 13:45           ` Joseph Reagle
2021-06-02 16:44       ` John MacFarlane [this message]
     [not found]         ` <m2r1hkusgl.fsf-pgq/RBwaQ+zq8tPRBa0AtqxOck334EZe@public.gmane.org>
2021-06-02 18:20           ` Joseph Reagle

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=m2r1hkusgl.fsf@johnmacfarlane.net \
    --to=jgm-tvlzxgkolnx2fbvcvol8/a@public.gmane.org \
    --cc=joseph.2011-T1oY19WcHSwdnm+yROfE0A@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).