Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Another ${(z)param} buglet
- X-seq: zsh-workers 28509
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-workers@xxxxxxx
- Subject: Re: Another ${(z)param} buglet
- Date: Thu, 09 Dec 2010 12:25:12 -0800
- In-reply-to: <20101209181632.27d47e95@xxxxxxxxxxxxxxxxxxxxxxxxx>
- List-help: <mailto:zsh-workers-help@zsh.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:zsh-workers@zsh.org>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <101207203441.ZM4340@xxxxxxxxxxxxxxxxxxxxxx> <20101208175103.40d6cc29@xxxxxxxxxxxxxxxxxxxxxxxxx> <101209074233.ZM8003@xxxxxxxxxxxxxxxxxxxxxx> <20101209181632.27d47e95@xxxxxxxxxxxxxxxxxxxxxxxxx>
On Dec 9, 6:16pm, Peter Stephenson wrote:
}
} On Thu, 09 Dec 2010 07:42:33 -0800
} Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
} > There isn't yet a (Z) flag; perhaps we could make that the equivalent
} > of turning on interactivecomments, and leave (z) as it was?
}
} Wondered about that, but there are so many possible tweaks to word
} splitting I'm trying to think of a more flexible way than simply two
} letters (that doesn't involve anything as gross as a shell option).
Perhaps leave (z) alone and introduce (Z:stuff:) where stuff can be
a set of controls for how the parse is applied?
Another possibility would be to introduce a builtin ala zparseopts that
dismantles the string and populates a hash, or something.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author