Re: Bash commands: maybe they want to drive us crazy?
From: Bill Unruh (unruh_at_string.physics.ubc.ca)
Date: 06/30/04
- Next message: Bill Unruh: "Re: rsync and file renaming"
- Previous message: Miriam Tolke: "more interrupts with APIC"
- In reply to: GP: "Bash commands: maybe they want to drive us crazy?"
- Next in thread: Paul Black: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: Paul Black: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: Floyd L. Davidson: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: GP: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: GP: "Re: Bash commands: maybe they want to drive us crazy?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Date: Wed, 30 Jun 2004 19:10:28 +0000 (UTC)
GP <gilpel@inverse.nretla.org> writes:
]Here's how to make a grep:
]grep [options] PATTERN [FILE...]
]Ex.:
]grep -ir IPv6 .
]Here's how to make a find:
]find [path...] [expression]
No. find [path] [options]
]find -iname . "*IPv6*"
-iname is an option which takes one argument. That argument to the option in this case is
'*IPV6*' (NOT "*IPv6*" because the latter would cause the shell to expand
the *s, not find) It is NOT an argument to find, it is an argument to the
option -iname.
Your format would make no sense whatsoever and would not correspond to any
format of any command.
]Oups! Doesn't work! No mention of options in the arrrg... SYNOPSIS! Here's how
]it should have been written:
]find [path...] [options] [expression]
NO NO NO.
find path [options]
Find has no expression as an argument.
]find . -iname "*IPv6*"
] From find to grep, everything is upside down.
No. The only thing backwards is that he path is first, because it would be
far to easy to loose sight of the path with a long list of options.
][expression], which corresponds to PATTERN is at the end rather than in the middle.
There is no pattern. There is an argument to various options.
][options] is in the middle instead of at the beginning.
][path...], which corresponds to FILE is at the beginning rather than at the end.
]Microsoft "suits" wouldn't let this happen.
?? They do not let commands happen. It is very difficult to run a command
in MS, and then the syntax is all over the place, and sometimes different
from Unix where they took it from.
- Next message: Bill Unruh: "Re: rsync and file renaming"
- Previous message: Miriam Tolke: "more interrupts with APIC"
- In reply to: GP: "Bash commands: maybe they want to drive us crazy?"
- Next in thread: Paul Black: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: Paul Black: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: Floyd L. Davidson: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: GP: "Re: Bash commands: maybe they want to drive us crazy?"
- Reply: GP: "Re: Bash commands: maybe they want to drive us crazy?"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ]
Relevant Pages
|