aboutsummaryrefslogtreecommitdiff
path: root/MANUAL.txt
diff options
context:
space:
mode:
authorJohn MacFarlane <jgm@berkeley.edu>2019-11-07 10:48:38 -0800
committerJohn MacFarlane <jgm@berkeley.edu>2019-11-07 10:48:38 -0800
commit9c7f75afb5d4e50ac915213eba0470c2d0ad304d (patch)
treee6c9e0e66d8cd9458ccaf2104abfb22946652bf5 /MANUAL.txt
parente299212bf766cdbeec43be90f634038ab4a727c1 (diff)
downloadpandoc-9c7f75afb5d4e50ac915213eba0470c2d0ad304d.tar.gz
Change merge behavior for metadata.
Previously, if a document contained two YAML metadata blocks that set the same field, the conflict would be resolved in favor of the first. Now it is resolved in favor of the second (due to a change in pandoc-types). This makes the behavior more uniform with other things in pandoc (such as reference links and `--metadata-file`).
Diffstat (limited to 'MANUAL.txt')
-rw-r--r--MANUAL.txt6
1 files changed, 3 insertions, 3 deletions
diff --git a/MANUAL.txt b/MANUAL.txt
index 2e37d62a0..207f5a5ae 100644
--- a/MANUAL.txt
+++ b/MANUAL.txt
@@ -3883,9 +3883,9 @@ given a role by external processors.) Field names must not be
interpretable as YAML numbers or boolean values (so, for
example, `yes`, `True`, and `15` cannot be used as field names).
-A document may contain multiple metadata blocks. The metadata fields will
-be combined through a *left-biased union*: if two metadata blocks attempt
-to set the same field, the value from the first block will be taken.
+A document may contain multiple metadata blocks. If two
+metadata blocks attempt to set the same field, the value from
+the second block will be taken.
When pandoc is used with `-t markdown` to create a Markdown document,
a YAML metadata block will be produced only if the `-s/--standalone`