summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorTakeshi KOMIYA <i.tkomiya@gmail.com>2021-10-09 16:26:52 +0900
committerGitHub <noreply@github.com>2021-10-09 16:26:52 +0900
commitbe36cf471b50739e3a686ea69db3db3d99aba2f2 (patch)
tree8aaead4e2d42fb32f714975d73cb9d9c0e51674d
parent15df18392a653fe7d6cae9316f391b759ec2f852 (diff)
parentee3f3619929d1dc9277c6081003cf58268029345 (diff)
downloadsphinx-git-be36cf471b50739e3a686ea69db3db3d99aba2f2.tar.gz
Merge pull request #9679 from latosha-maltba/doc/directive-indent
Document indent behaviour for directives
-rw-r--r--doc/usage/restructuredtext/basics.rst22
1 files changed, 21 insertions, 1 deletions
diff --git a/doc/usage/restructuredtext/basics.rst b/doc/usage/restructuredtext/basics.rst
index d96b1fe38..16cfc6109 100644
--- a/doc/usage/restructuredtext/basics.rst
+++ b/doc/usage/restructuredtext/basics.rst
@@ -410,7 +410,27 @@ following the arguments and indicated by the colons). Options must be indented
to the same level as the directive content.
The directive content follows after a blank line and is indented relative to
-the directive start.
+the directive start or if options are present, by the same amount as the
+options.
+
+Be careful as the indent is not a fixed number of whitespace, e.g. three, but
+any number whitespace. This can be surprising when a fixed indent is used
+throughout the document and can make a difference for directives which are
+sensitive to whitespace. Compare::
+
+ .. code-block::
+ :caption: A cool example
+
+ The output of this line starts with four spaces.
+
+ .. code-block::
+
+ The output of this line has no spaces at the beginning.
+
+In the first code block, the indent for the content was fixated by the option
+line to three spaces, consequently the content starts with four spaces.
+In the latter the indent was fixed by the content itself to seven spaces, thus
+it does not start with a space.
Images