Document wildcard differences in behavior.

Ideas for new features & functions

Moderators: Dorian (MJT support), JRL

Post Reply
gdyvig
Automation Wizard
Posts: 447
Joined: Fri Jun 27, 2008 7:57 pm
Location: Seattle, WA

Document wildcard differences in behavior.

Post by gdyvig » Fri May 01, 2009 4:07 pm

People have reported problems with wildcards, especially with the FTP commands as in the following link:

http://www.mjtnet.com/usergroup/viewtopic.php?t=5471


Wildcards are supported for several types of commands"
- Windows
- files
- ftp
- maybe more.

The precise behavior is documented for windows.
Example: SetFocus>part*
works for these windows: part
partlist
department
rampart
does not work:
*part
*part*

The behavior for ftp only supports a single asterisk in each folder level, filename, or extension (undocumented restriction).
works: mydir/*.*
mydir/*.txt
mydir/readme.*
does not work: mydir/read*.txt
mydir/read*.*
mydir/r*d*.txt

The behavior for files is supports multiple wildcards in combination with other text:
works: mydir/read*.txt
mydir/read*.*
mydir/r*d*.txt
m*d*/**d*.t*

The differences are confusing because they differ form each and also when compared to similar commands from other environments.

Please document in the user guide and help.

Post Reply
Sign up to our newsletter for free automation tips, tricks & discounts