From: Zoltan Hidvegi <hzoli@cs.elte.hu>
To: gene@bear.com
Cc: zsh-workers@math.gatech.edu (Zsh workers list)
Subject: Re: Re: is this really correct
Date: Mon, 10 Jun 1996 20:33:20 +0200 (MET DST) [thread overview]
Message-ID: <199606101833.UAA06977@bolyai.cs.elte.hu> (raw)
In-Reply-To: <9606101807.AA03486@bear.com> from "gene@bear.com" at "Jun 10, 96 02:07:15 pm"
> What is the "preferred" way of testing strings that may be arbitrarily
> input then given the above ? I mean one does not know what 'a' is until
> you do a test on it right ?
As I said I'll modify [ ... ] according to POSIX which will fix this
problem (maybe it was not clear that test and [ are the same). But in zsh
one can use
% a="-s"; if [[ "$a" = "-s" ]] then echo "yeh" ; fi
which should work with all zsh versions.
Zoltan
prev parent reply other threads:[~1996-06-10 18:43 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-06-10 18:07 gene
1996-06-10 18:33 ` Zoltan Hidvegi [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=199606101833.UAA06977@bolyai.cs.elte.hu \
--to=hzoli@cs.elte.hu \
--cc=gene@bear.com \
--cc=zsh-workers@math.gatech.edu \
/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).