DragonFly kernel List (threaded) for 2008-02
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]
Re: Globbing
er_reader.dragonflybsd.org> <47b34981$0$856$415eb37d@crater_reader.dragonflybsd.org> <20080213203349.e9caf15b.steve@sohara.org> <47b35e26$0$848$415eb37d@crater_reader.dragonflybsd.org> <47B36486.5060404@fs.ei.tum.de>
In-Reply-To: <47B36486.5060404@fs.ei.tum.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 7bit
Lines: 33
Message-ID: <47b37127$0$854$415eb37d@crater_reader.dragonflybsd.org>
NNTP-Posting-Host: 218.253.81.177
X-Trace: 1202942247 crater_reader.dragonflybsd.org 854 218.253.81.177
Xref: crater_reader.dragonflybsd.org dragonfly.kernel:12132
Simon 'corecode' Schubert wrote:
> Bill Hacker wrote:
>>>> After all, if use of find or xargs accomplishes the task w/o ill
>>>> effects on memory, then what prevents creation of a compiled utility
>>>> that has that same sort of 'flavor' of approach - just hard-wired
>>>> from the get-go?
>>> It would have to be a shell builtin
>> An assumption based on legacy.
>
> rm() {
> args=rm
> while [ "$#" -lt 0 ]
> do
> case "$1" in
> -*) args="$args $1"; shift ;;
> *) break ;;
> esac
> done
>
> echo "$@" | xargs $args
> }
>
Thanks,
I (think) I understand what it is expected to do, but have missed
something, as a cut n' paste hasn't (done that) yet.
Not in ksh anyway.
Example of syntax 'in use'? i.e. what to feed it...
Bill
[
Date Prev][
Date Next]
[
Thread Prev][
Thread Next]
[
Date Index][
Thread Index]