summaryrefslogtreecommitdiff
path: root/_doc/detail.rst
diff options
context:
space:
mode:
authorAnthon van der Neut <anthon@mnt.org>2016-04-19 10:09:54 +0200
committerAnthon van der Neut <anthon@mnt.org>2016-04-19 10:09:54 +0200
commit8ab6a692cc4cea1801dcf83157c333a67ca3d200 (patch)
tree4ad5b7d14a48dd65ec604afbf3d81794263f1200 /_doc/detail.rst
parente59d6cd34c3e9fa5df9da18448063aff96eb57f1 (diff)
downloadruamel.yaml-8ab6a692cc4cea1801dcf83157c333a67ca3d200.tar.gz
allow "indent=2, block_seq_indent=2"0.11.10
Diffstat (limited to '_doc/detail.rst')
-rw-r--r--_doc/detail.rst12
1 files changed, 8 insertions, 4 deletions
diff --git a/_doc/detail.rst b/_doc/detail.rst
index 19142e2..1449023 100644
--- a/_doc/detail.rst
+++ b/_doc/detail.rst
@@ -63,10 +63,14 @@ indentation::
- 2
-If the ``block_seq_indent`` is only one less than the indent, there is
-not enough room to put the space that has to follow the dash. In that
-case the element is pushed to the next line. If you specify ``block_seq_indent>=indent``, then the emitter adjusts the ``indent`` value to equal
-``block_seq_indent + 1``.
+If the ``block_seq_indent`` equals ``indent``, there is not enough
+room for the dash and the space that has to follow. In that case the
+element itself would normally be pushed to the next line (and older versions
+of ruamel.yaml did so). But this is
+prevented from happening. However the ``indent`` level is what is used
+for calculating the cumulative indent for deeper levels and specifying
+``indent=3`` resp. ``block_seq_indent=2``, gives correct, but counter
+intuitive results.
Positioning ':' in top level mappings, prefix in ':'
----------------------------------------------------