01-13-2002
To answer your question you'll need to tell us what you are trying to do...in what situation or with which command are you trying to use wildcards.
i.e are you trying to list files, or is it in a script...etc.
Please provide more info...
10 More Discussions You Might Find Interesting
1. Programming
Using a makefile I want to compile all .c files in the current directory without specifying them directly and then link their associated .o files into a library.
How do I do this ?
Thanks. (1 Reply)
Discussion started by: rcscott
1 Replies
2. UNIX for Dummies Questions & Answers
Hiya,
I want to list all files missing a certain pattern and/or filename pattern on the entire drive.
In DOS I would type (for instance):
dir \t*.doc /s /a
which should find all doc files whose filename starts with `t'.
How do I do that in a unix shell? Can it be done w/ ls at... (5 Replies)
Discussion started by: ropers
5 Replies
3. UNIX for Dummies Questions & Answers
I'm trying to delete lines from a large text file using VI.
Every line that I am wanting to delete start with 'S' - all others do not. (A list of users)
I've tried using * but doesn't seem to like it...any ideas...
Doesn't have to be VI - but I'm better with VI than sed/awk. (8 Replies)
Discussion started by: peter.herlihy
8 Replies
4. UNIX for Dummies Questions & Answers
when writing a shell script (bourne) and using a unix command like 'ls' is there anything special you need to do to use a wildcard (like *)? (3 Replies)
Discussion started by: benu302000
3 Replies
5. UNIX for Dummies Questions & Answers
ok, I'm trying to write a script file that lists files with specific elements in the name into a txt file, it looks like this
ls s*.dat > file_names.txt
can't figure out whats wrong with that line, any ideas?
thanks in advance (10 Replies)
Discussion started by: benu302000
10 Replies
6. UNIX for Dummies Questions & Answers
Hi All
Please excuse another straightforward question. When creating a tar archive from a directory I am attempting to use wildcards to eliminate certain filetypes (otherwise the archive gets too large). So I am looking for something along these lines.
tar -cf archive.tar * <minus all *.rst... (5 Replies)
Discussion started by: C3000
5 Replies
7. UNIX for Dummies Questions & Answers
Is there some rule about using wildcards in path? Say I want to create a file, but one of the directories in the path is called 1433d.default and on different machines it will be called <some other string>.default
touch ~/Library/Application/*.default/myfile
In theory I thought that... (5 Replies)
Discussion started by: glev2005
5 Replies
8. UNIX for Advanced & Expert Users
These 2 websites do a GREAT job of explaining different types of wildcards. I learned about the categories of characters which I never knew about at all.
GNU/Linux Command-Line Tools Guide - Wildcards
GREP (1 Reply)
Discussion started by: cokedude
1 Replies
9. Shell Programming and Scripting
Hello:
I have a very basic question. I'd like to select all files except for one file. For example, say I want to move all of the files in my current directory to a subdirectory called archive, I would use mv ./* archive/ But what if I want to move all files except for README.txt? Is there an... (19 Replies)
Discussion started by: Danny.Boy
19 Replies
10. UNIX for Dummies Questions & Answers
Hi, I'm new to Unix, but have a directory which has many files in it, well over 1000. The files are called :
M07GO.STOPE0001
M07GO.STOPE0002
M07GO.STOPE0003
M07GO.STOPE0004
etc...
I would like to rename them to the following :
M070001.bin
M070002.bin
M070003.bin
M070004.bin
etc....... (4 Replies)
Discussion started by: rnmuk
4 Replies
LEARN ABOUT DEBIAN
prophet::cli::command
Prophet::CLI::Command(3pm) User Contributed Perl Documentation Prophet::CLI::Command(3pm)
Registering argument translations
This is the Prophet CLI's way of supporting short forms for arguments, e.g. you want to let '-v' be able to used for the same purpose as
'--verbose' without dirtying your code checking both or manually setting them if they exist. We want it to be as easy as possible to have
short commands.
To use, have your command subclass do:
sub ARG_TRANSLATIONS { shift->SUPER::ARG_TRANSLATIONS(), f => 'file' };
You can register as many translations at a time as you want. The arguments will be translated when the command object is instantiated. If
an arg already exists in the arg translation table, it is overwritten with the new value.
require_uuid
Checks to make sure the uuid attribute is set. Prints an error and dies with the command's usage string if it is not set.
edit_text [text] -> text
Filters the given text through the user's $EDITOR using Proc::InvokeEditor.
edit_hash hash => hashref, ordering => arrayref
Filters the hash through the user's $EDITOR using Proc::InvokeEditor.
No validation is done on the input or output.
If the optional ordering argument is specified, hash keys will be presented in that order (with unspecified elements following) for edit.
If the record class for the current type defines a "immutable_props" routine, those props will not be presented for editing.
False values are not returned unless a prop is removed from the output.
edit_props arg => str, defaults => hashref, ordering => arrayref
Returns a hashref of the command's props mixed in with any default props. If the "arg" argument is specified, (default "edit", use "undef"
if you only want default arguments), then "edit_hash" is invoked on the property list.
If the "ordering" argument is specified, properties will be presented in that order (with unspecified props following) if filtered through
"edit_hash".
prompt_choices question
Asks user the question and returns 0 if answer was the second choice, 1 otherwise. (First choice is the default.)
prompt_Yn question
Asks user the question and returns true if answer was positive or false otherwise. Default answer is 'Yes' (returns true).
print_usage
Print the command's usage message to STDERR and die. Commands should implement "usage_msg", which returns the usage message.
If the usage message method needs arguments passed in, use a closure.
get_cmd_and_subcmd_names [no_type => 1]
Gets the name of the script that was run and the primary commands that were specified on the command-line. If a true boolean is passed in
as "no_type", won't add '<record-type>' to the subcmd if no type was passed in via the primary commands.
perl v5.10.1 2009-08-19 Prophet::CLI::Command(3pm)