Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: PATCH: zsh/files adjustments
- X-seq: zsh-workers 24976
- From: Peter Stephenson <pws@xxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxxxxx>
- Subject: Re: PATCH: zsh/files adjustments
- Date: Thu, 8 May 2008 10:05:35 +0100
- In-reply-to: <20080508060813.GA53310@xxxxxxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
- Organization: CSR
- References: <20080508060813.GA53310@xxxxxxxxxxxxxxxxxxxx>
On Wed, 7 May 2008 23:08:13 -0700
Phil Pennock <zsh-workers+phil.pennock@xxxxxxxxxxxx> wrote:
> This patch for zsh/files:
> * Updates the documentation to be more cautionary
> * Adds new binary names for the commands
> * Implements ln -h/-n to inhibit chasing symlinks
Looks OK and I've committed it.
> Is there any thought to being able to name groups of features, perhaps
> with a g: prefix, so that it becomes possible to do:
> zmodload -F zsh/files +g:zf_commands
> zmodload -F zsh/files -g:bare_commands
> ? Is this desirable? I'd view the semantics as batch-enable/disable,
> so that later items on the command-line override, even if more general.
Something like this is probably desirable, but we might get away with an
option to handle features based on pattern.
--
Peter Stephenson <pws@xxxxxxx> Software Engineer
CSR PLC, Churchill House, Cambridge Business Park, Cowley Road
Cambridge, CB4 0WZ, UK Tel: +44 (0)1223 692070
Messages sorted by:
Reverse Date,
Date,
Thread,
Author