zsh-workers
 help / color / mirror / code / Atom feed
From: ZyX <kp-pav@yandex.ru>
To: Eric Cook <llua@gmx.com>, "zsh-workers@zsh.org" <zsh-workers@zsh.org>
Subject: Re: [[ is being treated as a pattern in the command/reserved word position.
Date: Sun, 29 Mar 2015 00:36:48 +0300	[thread overview]
Message-ID: <6044831427578608@web3o.yandex.ru> (raw)
In-Reply-To: <55171842.7030505@gmx.com>

29.03.2015, 00:14, "Eric Cook" <llua@gmx.com>:
> With a recent build, this happens to me. Does it happen for anyone else?
>
> % type [[
> zsh: bad pattern: [[

This is expected: you open a collection, but do not close it.

> % type '[['
> [[ is a reserved word
> % '[[' a == a ]]
> zsh: = not found

`[[` is *not* a command. Neither it is a shell builtin. It is an extension to the shell syntax. So this is expected as well. You see exactly this error message because `=tty` expands to `/usr/bin/tty`.

> % '[[' a '==' a ]]
> zsh: command not found: [[

Same, but you got rid of `==` error.

> % print $ZSH_PATCHLEVEL
> zsh-5.0.7-0-g208bded

`[[` is a *syntax extension* which works *only* if `[[` (literally) occurs in command position. In first commented case you violate “in command position condition”, in other commented cases you violate “literally”.


  parent reply	other threads:[~2015-03-28 21:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-28 21:08 Eric Cook
2015-03-28 21:18 ` Eric Cook
2015-03-28 21:25 ` Eric Cook
2015-03-28 21:36 ` ZyX [this message]
2015-03-28 21:44 ` Bart Schaefer
2015-03-28 21:55   ` Eric Cook
2015-03-28 22:24     ` Bart Schaefer
2015-03-28 22:33       ` ZyX
2015-03-28 22:45         ` Bart Schaefer
2015-03-28 23:07         ` Eric Cook
2015-03-28 23:19           ` ZyX
2015-03-28 23:27             ` Eric Cook
2015-03-28 23:57               ` ZyX
2015-03-29  0:09                 ` Eric Cook
2015-03-28 22:44       ` Peter Stephenson
2015-03-28 22:48         ` 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=6044831427578608@web3o.yandex.ru \
    --to=kp-pav@yandex.ru \
    --cc=llua@gmx.com \
    --cc=zsh-workers@zsh.org \
    /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).