public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: bapt auguie <auguieba-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org
Subject: filter to inject raw TeX command based on header attributes
Date: Thu, 23 Dec 2021 16:14:50 +0100	[thread overview]
Message-ID: <CAGCXF28DUfNvU8cVDjydiqg+TUwzOhdrWL5w5xc8Ua-MXA6BBA@mail.gmail.com> (raw)

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

Hi,

I'd like to make use of pandoc's header attributes (
https://pandoc.org/MANUAL.html#extension-header_attributes) to inject a
custom LaTeX \renewcommand{} definition in specific sections. My goal is to
have a minimalist markdown file for my CV (no tables or raw LaTeX, just
simple lists and #headers), and have a Lua filter identify which sections
have specific formatting needs (e.g wrap inside a 3-column table), which
will be taken care of by LaTeX.

Consider this input markdown,


> # qualifications {#id1 .CV content=list}
>
> ## 2011 | can type, delete, copy and paste
> ## 2021 | can *format*, sometimes
>
> # work in progress {#id2 .CV content=freetext}
>
> ## Beside lists, I am hoping to learn to format free text too, *someday*.
>


I would like to walk the AST, and immediately after headers with a specific
attribute, inject a \renewcommand{} based on the header's attributes, such
as (dummy example),

\renewcommand\subsection[1]{\textbf{#1}}

for sections with content=list and

\renewcommand\subsection[1]{\textit{#1}}

with content=freetext.

This is obviously a contrived example, the actual command I'm using is
actually to split a sub-header and format it as a table (dates | job
position | location) or various other tasks (e.g. changing emphasis colours
for different sections etc.).

I'm not familiar enough with the pandoc AST or lua to figure this out; I
looked at a related example ( * noexport-subtrees.lua *
<https://gist.github.com/tarleb/a0f41adfa7b0e5a9be441e945f843299#file-noexport-subtrees-lua>)
but here the situation is a bit different, as I need to create an
additional element (raw tex string) and append it to the original header.

Many thanks,

baptiste

-- 
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/CAGCXF28DUfNvU8cVDjydiqg%2BTUwzOhdrWL5w5xc8Ua-MXA6BBA%40mail.gmail.com.

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

             reply	other threads:[~2021-12-23 15:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-23 15:14 bapt auguie [this message]
     [not found] ` <CAGCXF28DUfNvU8cVDjydiqg+TUwzOhdrWL5w5xc8Ua-MXA6BBA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-12-29 19:41   ` John MacFarlane
     [not found]     ` <m2a6gjyza0.fsf-jF64zX8BO0+FqBokazbCQ6OPv3vYUT2dxr7GGTnW70NeoWH0uzbU5w@public.gmane.org>
2021-12-29 20:45       ` bapt auguie
     [not found]         ` <CAGCXF2_r6G_sMQWmxyXKA5i29gRFLtOG5Z-WowKXkHASThsGqQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2021-12-31 11:52           ` BPJ

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=CAGCXF28DUfNvU8cVDjydiqg+TUwzOhdrWL5w5xc8Ua-MXA6BBA@mail.gmail.com \
    --to=auguieba-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).