zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Peter Stephenson <p.w.stephenson@ntlworld.com>, zsh-workers@sunsite.dk
Subject: Re: path and += troubles
Date: Sat, 26 Nov 2005 21:13:00 +0000	[thread overview]
Message-ID: <1051126211300.ZM1008@candle.brasslantern.com> (raw)
In-Reply-To: <200511261840.jAQIeKk0009266@pwslaptop.csr.com>

On Nov 26,  6:40pm, Peter Stephenson wrote:
} Subject: Re: path and += troubles
}
} > On Nov 25,  9:32pm, Steven Klass wrote:
} > }
} > } 		$1+=($2)
} > 
} > For some reason "setopt nullglob" (even cshnullglob) prevents the error
} > message that would otherwise be produced for this line, turning it into
} > a silent no-op.  I think that's probably an obscure bug.
} 
} It's a bug if you think the "=" should always indicate an assignment

No, that's not it.

} Otherwise, it looks like
} an expression with a set of globbing qualifiers at the end

Exactly ... the problem is this:

schaefer<508> echo $1+=($2)
zsh: no match
schaefer<509> $1+=($2)
schaefer<510> 

Where's my "no match" error in the second case?

} At the moment lexical analysis is fairly restrictive about what it will
} consider an assignment; if it doesn't like it, it will decide it's just
} an ordinary string, so the word will be parsed as a command.

That's just fine, and I don't think it should be changed.


  reply	other threads:[~2005-11-26 21:13 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1051126170046.ZM773@candle.brasslantern.com>
2005-11-26 18:40 ` Peter Stephenson
2005-11-26 21:13   ` Bart Schaefer [this message]
2005-11-27 13:34     ` Peter Stephenson
2005-11-27 18:40       ` Bart Schaefer
2005-11-27 20:39         ` Peter Stephenson
2005-11-28  1:15           ` Bart Schaefer

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=1051126211300.ZM1008@candle.brasslantern.com \
    --to=schaefer@brasslantern.com \
    --cc=p.w.stephenson@ntlworld.com \
    --cc=zsh-workers@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).