public inbox archive for pandoc-discuss@googlegroups.com
 help / color / mirror / Atom feed
From: Henrik Klang <henrik.klang-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
To: pandoc-discuss <pandoc-discuss-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
Subject: Re: Pandoc Lua script to filter specific markdown sub sections during PDF generation
Date: Wed, 9 Sep 2020 04:24:39 -0700 (PDT)	[thread overview]
Message-ID: <dea98b71-e65b-401e-b3df-338cd80ae369n@googlegroups.com> (raw)
In-Reply-To: <667487b4-f213-45c7-94fd-c0237d8b6592n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>


[-- Attachment #1.1: Type: text/plain, Size: 2273 bytes --]

Update: your suggestions worked. Thank you for excellent support.

tisdag 1 september 2020 kl. 12:05:48 UTC+2 skrev Henrik Klang:

> I meant the entire section with both headline and body.
>
> Thanks for the suggestions guys, I will try them out!
>
> / Henrik
>
> tisdag 1 september 2020 kl. 11:35:15 UTC+2 skrev Albert Krewinkel:
>
>>
>> Denis Maier writes:
>>
>> > You mean like removing the sub section header? Or the whole subsection 
>> until the
>> > start of the next section?
>> > Both should be possible with a lua filter. The first is trivial, the 
>> second
>> > more complex (at least for me ;-). But I doubt it wouldn't be possible.
>> > The tricky part is possibly that pandoc's AST does not reveal the 
>> hierarchy
>> > here:
>> >
>> > [Header 1 ("header-1",[],[]) [Str "Header",Space,Str "1"]
>> > ,Para [Str "Text"]
>> > ,Header 2 ("header-2",[],[]) [Str "Header",Space,Str "2"]
>> > ,Para [Str "Text"]
>> > ,Header 2 ("header-2-1",[],[]) [Str "Header",Space,Str "2"]
>> > ,Para [Str "Text"]
>> > ,Header 1 ("header-1-1",[],[]) [Str "Header",Space,Str "1"]
>> > ,Para [Str "Text"]]
>> >
>> > So, I imagine you have to walk over the AST and when you encounter a 
>> "Header 2"
>> > element, you delete this and everything else until you find the next 
>> "Head 1"
>> > element.
>>
>> That's a good approach. Untested Lua:
>>
>> local keep_deleting = false
>> function Block (b)
>> if b.t == 'Header' and b.level >= 3 then
>> keep_deleting = true
>> return {}
>> elseif b.t == 'Header' then
>> keep_deleting = false
>> elseif keep_deleting then
>> return {}
>> end
>> end
>>
>> The alternative is to let pandoc wrap all sections in divs and to delete
>> those that are undesired. See
>> https://gist.github.com/tarleb/a0f41adfa7b0e5a9be441e945f843299
>>
>>
>> --
>> Albert Krewinkel
>> GPG: 8eed e3e2 e8c5 6f18 81fe e836 388d c0b2 1f63 1124
>>
>

-- 
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/dea98b71-e65b-401e-b3df-338cd80ae369n%40googlegroups.com.

[-- Attachment #1.2: Type: text/html, Size: 3761 bytes --]

  parent reply	other threads:[~2020-09-09 11:24 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-09-01  8:01 Henrik Klang
     [not found] ` <4e07ae0a-dcb1-4f89-8b91-ba787b7bea1cn-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-01  8:28   ` Denis Maier
     [not found]     ` <92ac8df6-b88a-b047-b9f0-1fe62873b710-cl+VPiYnx/1AfugRpC6u6w@public.gmane.org>
2020-09-01  9:35       ` Albert Krewinkel
     [not found]         ` <87d035yh4n.fsf-9EawChwDxG8hFhg+JK9F0w@public.gmane.org>
2020-09-01 10:05           ` Henrik Klang
     [not found]             ` <667487b4-f213-45c7-94fd-c0237d8b6592n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-09 11:24               ` Henrik Klang [this message]
     [not found]                 ` <dea98b71-e65b-401e-b3df-338cd80ae369n-/JYPxA39Uh5TLH3MbocFFw@public.gmane.org>
2020-09-09 12:41                   ` Albert Krewinkel

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=dea98b71-e65b-401e-b3df-338cd80ae369n@googlegroups.com \
    --to=henrik.klang-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).