summaryrefslogtreecommitdiff
path: root/graphics/pgf/base/doc/text-en/pgfmanual-en-tikz-paths.tex
diff options
context:
space:
mode:
Diffstat (limited to 'graphics/pgf/base/doc/text-en/pgfmanual-en-tikz-paths.tex')
-rw-r--r--graphics/pgf/base/doc/text-en/pgfmanual-en-tikz-paths.tex7
1 files changed, 6 insertions, 1 deletions
diff --git a/graphics/pgf/base/doc/text-en/pgfmanual-en-tikz-paths.tex b/graphics/pgf/base/doc/text-en/pgfmanual-en-tikz-paths.tex
index 3a3f524eed..7e0cae5108 100644
--- a/graphics/pgf/base/doc/text-en/pgfmanual-en-tikz-paths.tex
+++ b/graphics/pgf/base/doc/text-en/pgfmanual-en-tikz-paths.tex
@@ -94,6 +94,11 @@ which is described in the subsections of the present section.
the path options (like filling and drawing the path due to a |fill| and a
|draw| option somewhere in the \meta{specification}), the nodes are added
in a post-processing step.
+
+ \emph{Note:} When scanning for path operations \tikzname\ expands tokens
+ looking for valid path operations. This however implies that these tokens
+ has to be fully expandable up to the point where it results in a valid path
+ operation.
\end{command}
\begin{key}{/tikz/name=\meta{path name}}
@@ -599,7 +604,7 @@ You can add a grid to the current path using the |grid| path operation.
This operations adds a grid filling a rectangle whose two corners are given
by \meta{corner} and by the previous coordinate. (Instead of a coordinate
you can also say |cycle| to use the position of the last move-to as the
- corner coordinate, but it not very natural to do so.) corner Thus, the
+ corner coordinate, but it not very natural to do so.) Thus, the
typical way in which a grid is drawn is |\draw (1,1) grid (3,3);|, which
yields a grid filling the rectangle whose corners are at $(1,1)$ and
$(3,3)$. All coordinate transformations apply to the grid.