New -find pseudo tests -use_pattern , -or_use_pattern
This commit is contained in:
@ -50,7 +50,7 @@
|
||||
@c man .\" First parameter, NAME, should be all caps
|
||||
@c man .\" Second parameter, SECTION, should be 1-8, maybe w/ subsection
|
||||
@c man .\" other parameters are allowed: see man(7), man(1)
|
||||
@c man .TH XORRISO 1 "Version 1.3.7, Apr 12, 2014"
|
||||
@c man .TH XORRISO 1 "Version 1.3.7, Apr 16, 2014"
|
||||
@c man .\" Please adjust this date whenever revising the manpage.
|
||||
@c man .\"
|
||||
@c man .\" Some roff macros, for reference:
|
||||
@ -2198,6 +2198,18 @@ to name length, permissible characters, and mandatory name components.
|
||||
If this test is reached and the tested file is a directory then -find will not
|
||||
dive into that directory. This test itself does always match.
|
||||
@*
|
||||
@item -use_pattern "on"|"off" :
|
||||
This pseudo test controls the interpretation of wildcards with tests
|
||||
-name, -wholename, and -disk_name. Default is "on". If interpretation
|
||||
is disabled by "off", then the parameters of -name, -wholename, and -disk_name
|
||||
have to match literally rather than as regular expression.
|
||||
This test itself does always match.
|
||||
@*
|
||||
@item -or_use_pattern "on"|"off" :
|
||||
Like -use_pattern, but automatically appending the test by -or rather
|
||||
than by -and. Further the test itself does never match. So a subsequent
|
||||
test -or will cause its other operand to be performed.
|
||||
@*
|
||||
@item -decision "yes"|"no" :
|
||||
If this test is reached then the evaluation ends immediately and action
|
||||
is performed if the decision is "yes" or "true". See operator -if.
|
||||
|
Reference in New Issue
Block a user