zsh-users
 help / color / mirror / code / Atom feed
From: Philippe Troin <phil@fifi.org>
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: zsh-users@sunsite.dk
Subject: Re: Defining commands to not evaluate certain metacharacters
Date: 21 Dec 2003 20:29:14 -0800	[thread overview]
Message-ID: <87ptehh3vp.fsf@ceramic.fifi.org> (raw)
In-Reply-To: <1031221065317.ZM3399@candle.brasslantern.com>

Bart Schaefer <schaefer@brasslantern.com> writes:

> 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?

I have no clue how it would work. I've just said I felt the need for
such a thing at some point, namely while trying to avoid quoting when
using zmv.
 
> 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?

Let's not put yacc into zsh (yet).

Phil.


      reply	other threads:[~2003-12-22  4:29 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2003-12-20 18:39 Lloyd Zusman
2003-12-21  1:32 ` Bart Schaefer
2003-12-21  1:38   ` Philippe Troin
2003-12-21  6:53     ` Bart Schaefer
2003-12-22  4:29       ` Philippe Troin [this message]

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87ptehh3vp.fsf@ceramic.fifi.org \
    --to=phil@fifi.org \
    --cc=schaefer@brasslantern.com \
    --cc=zsh-users@sunsite.dk \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.vuxu.org/mirror/zsh/

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).