From: Robert Kingett <kingettspeaks-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: How do you change the output directory
Date: Sun, 12 Feb 2023 07:48:44 -0800 (PST) [thread overview]
Message-ID: <f9089c8d-e19b-4652-a068-215591b1446bn@googlegroups.com> (raw)
In-Reply-To: <20150201065056.GD12964-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
[-- Attachment #1.1: Type: text/plain, Size: 2035 bytes --]
I know this is an old thread, but I am trying to create a folder with many
outputs. I tried to follow the thread but, upon exporting, I keep getting
an invalid argument error.
I am trying to batch all inputs from a folder into a subfolder inside the
same directory, so that all outputs are in a different folder.
I've tried the following but it is not creating the folder and putting
files in that folder.
gci -r -i *.docx |foreach{$md=$_.directoryname+"\"+$_.basename+".md";pandoc
-f docx --wrap=none -s $_.name -o here/$md}
On Sunday, February 1, 2015 at 12:51:10 AM UTC-6 John MacFarlane wrote:
> Sure. Assuming you're in C:\Example, you could do
>
> pandoc myfile.txt -s -o here\myfile.html
>
> Or, if you're somewhere else,
>
> pandoc C:\Example\myfile.txt -s -o C:\Example\here\myfile.html
>
> +++ Darren Doyle [Jan 31 15 20:33 ]:
> >Let's say I had a markdown document located in C:\Example.
> >If I converted it to HTML can I set the output directory for that file to
> a
> >different folder (C:\Example\here)?
> >
> >--
> >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-discus...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> >To post to this group, send email to pandoc-...-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
> >To view this discussion on the web visit
> https://groups.google.com/d/msgid/pandoc-discuss/e185159b-34cb-4dcb-9825-cb842a876b4e%40googlegroups.com
> .
> >For more options, visit https://groups.google.com/d/optout.
>
>
--
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/f9089c8d-e19b-4652-a068-215591b1446bn%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 3421 bytes --]
prev parent reply other threads:[~2023-02-12 15:48 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 4:33 Darren Doyle
[not found] ` <e185159b-34cb-4dcb-9825-cb842a876b4e-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2015-02-01 6:50 ` John MacFarlane
[not found] ` <20150201065056.GD12964-bi+AKbBUZKbivNSvqvJHCtPlBySK3R6THiGdP5j34PU@public.gmane.org>
2015-02-01 18:45 ` Darren Doyle
2023-02-12 15:48 ` Robert Kingett [this message]
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=f9089c8d-e19b-4652-a068-215591b1446bn@googlegroups.com \
--to=kingettspeaks-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).