zsh-workers
 help / color / mirror / code / Atom feed
From: Peter Stephenson <pws@ibmth.df.unipi.it>
To: "Zsh hackers list" <zsh-workers@sunsite.auc.dk>
Subject: Re: PATCH: pws-21: parentheses in command word
Date: Wed, 09 Jun 1999 09:50:45 +0200	[thread overview]
Message-ID: <9906090750.AA17477@ibmth.df.unipi.it> (raw)
In-Reply-To: ""Andrej Borsenkow""'s message of "Wed, 09 Jun 1999 12:11:52 DFT." <003201beb24f$bb2aafd0$21c9ca95@mow.siemens.ru>

"Andrej Borsenkow" wrote:
> |
> |*** Src/lex.c.icp      Mon Jan 25 14:59:49 1999
> |--- Src/lex.c.orig     Tue Jun  8 12:28:02 1999
> --------------------------
> File to patch: 
> 
> Is it my patch so dumb?

Sorry, I originally made the patch after applying something sent by Sven,
so it doesn't apply to Src/lex.c as it should.

*** Src/lex.c		Mon Jan 25 14:59:49 1999
--- Src/lex.c.orig	Tue Jun  8 12:28:02 1999
***************
*** 898,906 ****
--- 898,917 ----
  		    e = hgetc();
  		    hungetc(e);
  		    lexstop = 0;
+ #if 1
+ 		    /* For command words, parentheses are only
+ 		     * special at the start.  But now we're tokenising
+ 		     * the remaining string.  So I don't see what
+ 		     * the old incmdpos test here is for.
+ 		     *   pws 1999/6/8
+ 		     */
+ 		    if (e == ')')
+ 			goto brk;
+ #else
  		    if (e == ')' ||
  			(incmdpos && !brct && peek != ENVSTRING))
  			goto brk;
+ #endif
  		}
  		pct++;
  	    }

-- 
Peter Stephenson <pws@ibmth.df.unipi.it>       Tel: +39 050 844536
WWW:  http://www.ifh.de/~pws/
Dipartimento di Fisica, Via Buonarroti 2, 56127 Pisa, Italy


      reply	other threads:[~1999-06-09  8:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
1999-06-08 12:06 Peter Stephenson
1999-06-08 14:51 ` Bart Schaefer
1999-06-08 14:30   ` Peter Stephenson
1999-06-09  8:11 ` Andrej Borsenkow
1999-06-09  7:50   ` Peter Stephenson [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=9906090750.AA17477@ibmth.df.unipi.it \
    --to=pws@ibmth.df.unipi.it \
    --cc=zsh-workers@sunsite.auc.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).