aboutsummaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorBoris Kolpackov <boris@codesynthesis.com>2022-01-16 14:19:30 +0200
committerBoris Kolpackov <boris@codesynthesis.com>2022-01-16 14:19:30 +0200
commit54c56af1067df562c232cb73b9a1b85f67d9bbf1 (patch)
tree573f87f7fc0434b28e8f6cb0ca1952bc52f1c92c
parent5d425b7578484e7feeaa94d419f5c4bb5ea28475 (diff)
Expand on extension escaping in manual
-rw-r--r--doc/manual.cli10
1 files changed, 8 insertions, 2 deletions
diff --git a/doc/manual.cli b/doc/manual.cli
index 179024a..4fb8f5a 100644
--- a/doc/manual.cli
+++ b/doc/manual.cli
@@ -4147,8 +4147,14 @@ specified for our source files.
\N|If you need to specify a name that does not have an extension, then end it
with a single dot. For example, for a header \c{utility} you would write
-\c{hxx{utility.\}}. If you need to specify a name with an actual trailing
-dot, then escape it with a double dot, for example, \c{hxx{utility..\}}.|
+\c{hxx{utility.\}}. If you need to specify a name with an actual trailing dot,
+then escape it with a double dot, for example, \c{hxx{utility..\}}.
+
+More generally, anywhere in a name, a double dot can be used to specify a dot
+that should not be considered the extension separator while a triple dot \-
+which should. For example, in \c{obja{foo.a.o\}} the extension is \c{.o} and
+if instead we wanted \c{.a.o} to be considered the extension, then we could
+rewrite it either as \c{obja{foo.a..o\}} or as \c{obja{foo...a.o\}}.|
The next couple of lines set target type/pattern-specific variables to treat
all unit test executables as tests that should not be installed: