Browse Prior Art Database

Method of Complex Wildcard File Specifications

IP.com Disclosure Number: IPCOM000111474D
Original Publication Date: 1994-Feb-01
Included in the Prior Art Database: 2005-Mar-26
Document File: 2 page(s) / 46K

Publishing Venue

IBM

Related People

Johnson, WJ: AUTHOR [+2]

Abstract

Prior art provides the user with the ability to define a file specification by using a wildcard designation, an enhanced wildcard designation, or an "or" wildcard operation. A simple wildcard definition might be "abc.e*" whereby any file with a file name of "abc" and a file type beginning with "e" would satisfy this definition. An enhanced wildcard definition might be "a#zbc.*" whereby any file with a file name starting with either "abc" or "zbc" would satisfy this definition. An "or" wild card operation might be illustrated by "*.exe|dll|cmd|com" which would list all the executables in a directory. However, as wildcard definitions and operations become more complex, the amount of typing in creases for the user. The user needs a shortcut method of entering complex file specifications.

This text was extracted from an ASCII text file.
This is the abbreviated version, containing approximately 63% of the total text.

Method of Complex Wildcard File Specifications

      Prior art provides the user with the ability to define a file
specification by using a wildcard designation, an enhanced wildcard
designation, or an "or" wildcard operation.  A simple wildcard
definition might be "abc.e*" whereby any file with a file name of
"abc" and a file type beginning with "e" would satisfy this
definition.  An enhanced wildcard definition might be "a#zbc.*"
whereby any file with a file name starting with either "abc" or "zbc"
would satisfy this definition.  An "or" wild card operation might be
illustrated by "*.exe|dll|cmd|com" which would list all the
executables in a directory.  However, as wildcard definitions and
operations become more complex, the amount of typing in creases for
the user.  The user needs a shortcut method of entering complex file
specifications.

      This system provides a file specifications profile which can be
preconfigured by the user to eliminate verbose typing of complex file
specifications.  For example, with the prior art, in order to request
a directory listing of all the executables in a directory, the user
would have to type this command:

  dir *.exe|dll|cmd|com

      With this new system, the user can preconfigure an entry in the
file specification profile which equates "@x" to "exe|dll|cmd|com",
so the command to list all the executables is simplified to:

  dir *.@x
such that x is a file path.

      With the new system, the user eliminat...