From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29121 invoked from network); 21 Dec 2003 06:53:32 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 21 Dec 2003 06:53:32 -0000 Received: (qmail 21453 invoked by alias); 21 Dec 2003 06:53:19 -0000 Mailing-List: contact zsh-users-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 6938 Received: (qmail 21415 invoked from network); 21 Dec 2003 06:53:19 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 21 Dec 2003 06:53:19 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [4.11.8.53] by sunsite.dk (MessageWall 1.0.8) with SMTP; 21 Dec 2003 6:53:19 -0000 Received: (from schaefer@localhost) by candle.brasslantern.com (8.11.6/8.11.6) id hBL6rH503400 for zsh-users@sunsite.dk; Sat, 20 Dec 2003 22:53:17 -0800 X-Authentication-Warning: candle.brasslantern.com: schaefer set sender to schaefer@closedmail.com using -f From: Bart Schaefer Message-Id: <1031221065317.ZM3399@candle.brasslantern.com> Date: Sun, 21 Dec 2003 06:53:17 +0000 In-Reply-To: <87fzffvtk5.fsf@ceramic.fifi.org> Comments: In reply to Philippe Troin "Re: Defining commands to not evaluate certain metacharacters" (Dec 20, 5:38pm) References: <1031221013206.ZM3220@candle.brasslantern.com> <87fzffvtk5.fsf@ceramic.fifi.org> X-Mailer: Z-Mail (5.0.0 30July97) To: zsh-users@sunsite.dk Subject: Re: Defining commands to not evaluate certain metacharacters MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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?