Zsh Mailing List Archive
Messages sorted by:
Reverse Date,
Date,
Thread,
Author
Re: Defining commands to not evaluate certain metacharacters
- X-seq: zsh-users 6938
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: zsh-users@xxxxxxxxxx
- Subject: Re: Defining commands to not evaluate certain metacharacters
- Date: Sun, 21 Dec 2003 06:53:17 +0000
- In-reply-to: <87fzffvtk5.fsf@xxxxxxxxxxxxxxxx>
- Mailing-list: contact zsh-users-help@xxxxxxxxxx; run by ezmlm
- References: <m3y8t7jpv5.fsf@xxxxxxxxxx> <1031221013206.ZM3220@xxxxxxxxxxxxxxxxxxxxxxx> <87fzffvtk5.fsf@xxxxxxxxxxxxxxxx>
On Dec 20, 5:38pm, Philippe Troin wrote:
}
} How hard would it be implementing a "noparse" precommand modifier?
What does "noparse" mean? It's got to begin parsing before it can
recognize a precommand modifier. Even splitting into words at whitespace
is parsing, of a sort.
Do backslashes still work? What about quotes of various flavors? Care
to predict every possible question of this kind that I might ask?
If there isn't _some_ syntax, you're just using "cat" as your shell; the
input can't be processed in any useful way.
If you want to be able to define your own arbitrary syntax, you need a
language-definition language (like a YACC grammar). How hard would it
be to implement that?
Messages sorted by:
Reverse Date,
Date,
Thread,
Author