You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Allow the end user to use wildcards on the command line, but also allow the programmer to create aliases that use wildcards. This should conform to the basic bash wildcard syntax; but all that should be immediately implemented are the following two wildcards:
* to match a number of characters
? to match a single character
Ideally, this is provided in two forms:
For the commandline, which takes the wildcard input and matches it against files in the current working directory
For client-specified command aliases, which provides additional functionality to convert special alias rules into regularly-formatted commands
For example, the alias f(?) would map to something like f -x $1, where $1 is the first wildcard match in the alias
The text was updated successfully, but these errors were encountered:
Allow the end user to use wildcards on the command line, but also allow the programmer to create aliases that use wildcards. This should conform to the basic bash wildcard syntax; but all that should be immediately implemented are the following two wildcards:
*
to match a number of characters?
to match a single characterIdeally, this is provided in two forms:
f(?)
would map to something likef -x $1
, where$1
is the first wildcard match in the aliasThe text was updated successfully, but these errors were encountered: