From a0577305165ea4116ea72b5529c61966eea1c6e9 Mon Sep 17 00:00:00 2001 From: Boris Kolpackov Date: Wed, 31 May 2017 11:07:18 +0200 Subject: Refine testscript cleanup spec wrt wildcards --- doc/testscript.cli | 24 +++++++++++++----------- 1 file changed, 13 insertions(+), 11 deletions(-) (limited to 'doc/testscript.cli') diff --git a/doc/testscript.cli b/doc/testscript.cli index 79dcbce..685915e 100644 --- a/doc/testscript.cli +++ b/doc/testscript.cli @@ -2150,17 +2150,19 @@ The path components may contain the \c{*} and \c{?} wildcard characters with the following semantics: \ -? - any single character -* - all immediate files -*/ - all immediate sub-directories (which must be empty) -** - all files recursively -**/ - all sub-directories recursively (which must be empty) -*** - all files and sub-directories recursively as well as the start - directory itself -\ - -For example, the following cleanup will remove \c{dir/} and its content -recursively. +? - any single character +* - all immediate files +*/ - all immediate sub-directories (which must be empty) +** - all files recursively +**/ - all sub-directories recursively (which must be empty) +***/ - all sub-directories recursively (which must be empty) + as well as the start directory itself +\ + +In addition, if the last component in the path is \c{***} (without trailing +directory separator), then it matches all files and sub-directories +recursively as well as the start directory itself. For example, the following +cleanup will remove \c{dir/} and its content recursively. \ $* &dir/*** -- cgit v1.1