public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: William Lupton <wlupton-QSt+ys/nuMyEUIsrzH9SikB+6BGkLq7r@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: External default files specified in the YAML section of a Markdown file
Date: Fri, 10 Jun 2022 17:31:12 +0100	[thread overview]
Message-ID: <CAEe_xxgEvEhGY2kVfuMLteaXUpHfYOpZG4LLXW2fN5jt2=79tA@mail.gmail.com> (raw)
In-Reply-To: <e80a4dce-27f5-4379-a44f-5f43af197cc9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>

[-- Attachment #1: Type: text/plain, Size: 2788 bytes --]

i think you need to distinguish defaults (command-line options) and
metadata (although perhaps there's some overlap?).

this works:

% cat file.md   # I don't think you can specify the name of the defaults
file here, so I removed it; also not sure about ${.}
---
title: This is a simple Markdown file
author: Emiliano
---

# Heading

This is the content of the section.

% cat defaults.yaml
pdf-engine: wkhtmltopdf

% cat config.yaml
lang: en-US
papersize: a4
linestretch: 1.5
mainfont: "Palatino"
geometry:
  - top=2.5cm
  - left=3cm
  - right=3cm
  - bottom=2.5cm

% pandoc --defaults defaults.yaml --metadata-file config.yaml file.md -o
file.pdf
Loading pages (1/6)
Counting pages (2/6)
Resolving links (4/6)
Loading headers and footers (5/6)
Printing pages (6/6)
Done

On Fri, 10 Jun 2022 at 17:06, Emiliano <gattulli.emiliano-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org> wrote:

> Hello everyone!
>
> I'm trying to simplify the YAML section of my Markdown files by writing
> most of my settings in a separate default file or metadata file. The idea
> is to write just a few lines of YAML in my Markdown file and then having a
> separate file (let's call it config.yaml) in which I can set everything
> else. Let me provide a practical example:
>
> > file.md
> ```markdown
> ---
> title: This is a simple Markdown file
> author: Emiliano
> default: ${.}/config.yaml
> ---
>
> # Heading
>
> This is the content of the section.
> ```
>
> > config.yaml
> ```yaml
> ---
> lang: en-US
> papersize: a4
> linestretch: 1.5
> mainfont: "Palatino"
> geometry:
>   - top=2.5cm
>   - left=3cm
>   - right=3cm
>   - bottom=2.5cm
> pdf-engine: xelatex
> ---
> ```
>
> This very example I provided does not work! Do you have any idea of how to
> solve this issue?
>
> Many thanks in advance!
> Emiliano
>
> --
> 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/e80a4dce-27f5-4379-a44f-5f43af197cc9n%40googlegroups.com
> <https://groups.google.com/d/msgid/pandoc-discuss/e80a4dce-27f5-4379-a44f-5f43af197cc9n%40googlegroups.com?utm_medium=email&utm_source=footer>
> .
>

-- 
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/CAEe_xxgEvEhGY2kVfuMLteaXUpHfYOpZG4LLXW2fN5jt2%3D79tA%40mail.gmail.com.

[-- Attachment #2: Type: text/html, Size: 4351 bytes --]

  parent reply	other threads:[~2022-06-10 16:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-06-10 16:06 Emiliano
     [not found] ` <e80a4dce-27f5-4379-a44f-5f43af197cc9n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2022-06-10 16:31   ` William Lupton [this message]
     [not found]     ` <CAEe_xxgEvEhGY2kVfuMLteaXUpHfYOpZG4LLXW2fN5jt2=79tA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2022-06-12 14:19       ` Emiliano

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='CAEe_xxgEvEhGY2kVfuMLteaXUpHfYOpZG4LLXW2fN5jt2=79tA@mail.gmail.com' \
    --to=wlupton-qst+ys/numyeuisrzh9sikb+6bgklq7r@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).