wildcards_ccase

Wildcard (pattern-matching) characters are recognized in these contexts:

• UNIX and Linux: 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@@2006-03-04T22: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:

  Z:\> cleartool ls *.c	Fails; command shell does not understand wildcards.
  Z:\> cleartool lsvob *src*	“Pattern” argument wildcards accepted; no quotes required because cleartool does not expand the command line.

• 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” argument; quotes required
  cleartool> ls *.c	Standard pname argument; 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 recognizes these wildcard characters:

For more information, including restrictions, see config_spec.