From: "'rufus42' via pandoc-discuss" <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Defaults file: How to define different output formats?
Date: Tue, 24 Jan 2023 12:48:04 -0800 (PST) [thread overview]
Message-ID: <e020183e-c909-48df-8a26-7ec9c51fadban@googlegroups.com> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1683 bytes --]
Hello everyone,
First of all, a very big thank you for Pandoc.
I use it almost daily and always discover new possibilities.
I'm trying to put much-used standards into defaults files.
Is it possible to define _different_ output formats in _one_ defaults file?
If so, I would appreciate some help on how this defaults file should look
like.
(I am a complete yaml beginner).
If this is the wrong forum for such "beginner questions" please tell me,
where I can ask this question.
Thank you for your time and best regards to all
----
Translated with www.DeepL.com/Translator (free version) from original
german text.
Hallo miteinander,
als Erstes ein ganz ganz großes Danke für Pandoc.
Ich benutze es fast täglich und entdecke immer neue Möglichkeiten.
Ich versuche, vielbenutzte Standards in Defaults-Files zu packen.
Ist es möglich, in _einer_ Defaults-Datei _verschiedene_ Ausgabeformate zu
definieren?
Falls ja, würde ich mich über eine Hilfestellung freuen, wie diese
Defaults-Datei aussehen muss.
(Bin absoluter yaml-Anfänger)
Falls dies das falsche Forum für solche "Anfänger-Fragen" verratet mir
bitte. wo ich diese Frage stellen kann.
Vielen Dank für eure Zeit und liebe Grüße an alle
--
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/e020183e-c909-48df-8a26-7ec9c51fadban%40googlegroups.com.
[-- Attachment #1.2: Type: text/html, Size: 2146 bytes --]
reply other threads:[~2023-01-24 20:48 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=e020183e-c909-48df-8a26-7ec9c51fadban@googlegroups.com \
--to=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).