Pattern-matching characters for ClearCase and ClearCase LT pathnames
NOTE: For Attache, see the wildcards reference page.
Product | Command Type |
---|---|
ClearCase | general information |
ClearCase LT | general information |
Platform |
---|
UNIX |
Windows |
Wildcard (pattern-matching) characters are recognized in these contexts:
UNIX-cleartool single-command mode-The operating system shell, not cleartool, interprets pathnames and expands wildcards. With some cleartool commands (catcr -select, find -name, lsvob), you can specify a pathname pattern as a quoted argument; these are always interpreted by cleartool:
cleartool catcr -select "bug?.o" bgrs@@04-Mar.22:54.426
Windows-cleartool single-command mode-The command shell, not cleartool, interprets pathnames and expands wildcards. Therefore, unless you are using a command shell that expands pathname wildcards (cmd.exe does not), these wildcards are disallowed. You can, however, use wildcards in special pattern arguments in some cleartool subcommands (catcr -select, find -name, and lsvob). For example:
cleartool interactive mode-cleartool expands wildcards in pathnames. In cleartool commands that accept pattern arguments (catcr -select, find -name, and lsvob), you must quote a wildcard pattern to protect it from evaluation by cleartool itself. For example:
cleartool> lsvob -region "dev*" "*src*" |
("pattern" arg; quotes required) |
cleartool> ls *.c |
(standard pname arg; no quotes required) |
Config spec rules - The pathname pattern in a config spec rule is interpreted by a view's associated view_server process.
ClearCase and ClearCase LT recognize these wildcard characters:
See the config_spec reference page for more information, including restrictions.
Feedback on the documentation in this site? We welcome any comments!
Copyright © 2001 by Rational Software Corporation. All rights reserved. |