Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Emulating 'locate'
- X-seq: zsh-users 6645
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Emulating 'locate'
- Date: Sun, 5 Oct 2003 15:57:33 +0000
- In-reply-to: <m365j4oamc.fsf@xxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <20031001221753.GA23189@DervishD> <1031002023639.ZM22046@xxxxxxxxxxxxxxxxxxxxxxx> <20031002080358.GA23230@DervishD> <m365j6watm.fsf@xxxxxxxxxx> <20031004104844.GA50@DervishD> <m3oewxru4k.fsf@xxxxxxxxxx> <1031004163727.ZM28731@xxxxxxxxxxxxxxxxxxxxxxx> <m3isn4ol1q.fsf@xxxxxxxxxx> <1031004224016.ZM29064@xxxxxxxxxxxxxxxxxxxxxxx> <m365j4oamc.fsf@xxxxxxxxxx>
On Oct 4, 7:18pm, Lloyd Zusman wrote:
}
} Therefore, prior to the function definition, I now do this:
}
} { unalias xlocate; unfunction xlocate } 2>/dev/null
}
} But besides that, would another way to prevent this problem be to always
} define functions with "function foo" instead of "foo()"?
Yes, the latter will work. Note, however, that in ksh the meanings of
"foo() {...}" and "function foo {...}" are not quite equivalent, and
the zsh/ksh/bash developers have been discussing standardization of
some of those kinds of details, so there's a very small chance that in
the future you won't always be able to use them interchangeably.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author