Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Defining commands to not evaluate certain metacharacters
- X-seq: zsh-users 6937
- From: Philippe Troin <phil@xxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Defining commands to not evaluate certain metacharacters
- Date: 20 Dec 2003 17:38:34 -0800
- Cc: zsh-users@xxxxxxxxxx
- In-reply-to: <1031221013206.ZM3220@xxxxxxxxxxxxxxxxxxxxxxx>
- Mail-copies-to: nobody
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <m3y8t7jpv5.fsf@xxxxxxxxxx> <1031221013206.ZM3220@xxxxxxxxxxxxxxxxxxxxxxx>
- Sender: Philippe Troin <phil@xxxxxxxx>
Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> writes:
> On Dec 20, 1:39pm, Lloyd Zusman wrote:
> }
> } I want to define a set of commands that I can execute from the command
> } line under zsh.
>
> This is very nearly a non-starter. The shell parses shell syntax, not
> the syntax of some other language.
>
> You can get part of the way there with the "noglob" precommand modifier,
> but that doesn't change the special meanings of parentheses, braces, or
> redirections.
How hard would it be implementing a "noparse" precommand modifier?
I've also been wanting to use such a construct, for example when using
the zmv contributed function.
Phil.
Messages sorted by:
Reverse Date,
Date,
Thread,
Author