From: Bart Schaefer <schaefer@brasslantern.com>
To: Lyre <4179e1@gmail.com>, zsh-users@zsh.org
Subject: Re: string equal problem
Date: Mon, 07 Mar 2011 01:26:25 -0800 [thread overview]
Message-ID: <110307012625.ZM9254@torch.brasslantern.com> (raw)
In-Reply-To: <AANLkTi=GJPW=cVoA5hxbgVLsVMpeFehiZFjjU-dd04ow@mail.gmail.com>
On Mar 7, 5:04pm, Lyre wrote:
} Subject: string equal problem
}
} if [ "abc" == "def" ]; then echo y; else echo n; fi
}
} doesn't work, it says "zsh: = not found".
14.7.3 `=' expansion
--------------------
If a word begins with an unquoted `=' and the EQUALS option is set, the
remainder of the word is taken as the name of a command. If a command
exists by that name, the word is replaced by the full pathname of the
command.
What the doc doesn't go on to say is that if a command does NOT exist
by that name, it's an error.
The "test" command/builtin, for which "[" is an alias, doesn't normally
allow "==" as an operator; rather, it uses "=" for this comparison.
/usr/bin/test: ==: binary operator expected
As it happens, zsh does allow == as an operator for test, but you must
either quote it or unsetopt EQUALS, because the arguments of test are
subject to filename expansion.
If you want to use == without messing with the option, try this way:
if [[ "abc" == "def" ]]; then echo y; else echo n; fi
The "[[" reserved word imposes different parsing rules on the expression
it introduces, so there == is not subject to expansion.
} All of them doesn't work, except the zsh 4.2.0 on sles9.
SUSE must unsetopt EQUALS in /etc/zshenv, or some other startup file,
because no zsh since around version 2 (maybe longer) has been different
in this regard.
prev parent reply other threads:[~2011-03-07 9:26 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-03-07 9:04 Lyre
2011-03-07 9:13 ` Mikael Magnusson
2011-03-07 9:13 ` Frank Terbeck
2011-03-07 9:27 ` Frank Terbeck
2011-03-07 9:58 ` Micah Elliott
2011-03-07 9:15 ` Wendell Hom
2011-03-07 9:26 ` Bart Schaefer [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=110307012625.ZM9254@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=4179e1@gmail.com \
--cc=zsh-users@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).