mergable metadata blocks

mergable metadata blocks

[Thell Fowler]

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

Currently all blocks are merged such that first definition is sacred but 
what if a suffix indicator told the reader what to do. Since block merging 
is done at the reader a filter doesn't get the chance to process/merge 
duplicate keys in various blocks leaving pre-processing or a filter that 
reparses the original text. I'm currently pre-processing with jq for inline 
'includes' information.

But what if a reader was told what to do?

ie.

- normal:

- ignorable_:

- mergeable?:

- important!:

Possible at the filter level? Desirable? What do you think?

---

This, along with the posts on the 

YAML metadata raw fields [was: Use of RCS with pandoc YAML blocks]

thread could make for a quite powerful control mechanism.

-- 
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 post to this group, send email to pandoc-discuss-/JYPxA39Uh5TLH3MbocFF+G/Ez6ZCGd0@public.gmane.org
To view this discussion on the web visit https://groups.google.com/d/msgid/pandoc-discuss/3c6501ea-0eaa-4775-84b8-075cce17d964%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

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