From: Zefram <A.Main@dcs.warwick.ac.uk>
To: carlos@riglos.fisica.ufpr.br (Carlos Carvalho)
Cc: zsh-workers@math.gatech.edu
Subject: Re: problem with multicomp
Date: Fri, 2 Aug 1996 20:45:32 +0100 (BST) [thread overview]
Message-ID: <19129.199608021945@stone.dcs.warwick.ac.uk> (raw)
In-Reply-To: <m0umPXr-00002aC@riglos.fisica.ufpr.br> from "Carlos Carvalho" at Aug 2, 96 04:05:00 pm
>Yes, this is the problem. Thanks. HOWEVER, if I do setopt|grep set it
>doesn't appear!!
The correct way to check for an option being set is `[[ -o name ]]`.
`[[ -o nounset ]]` still works, and means exactly the same thing it
used to.
-zefram
prev parent reply other threads:[~1996-08-02 20:43 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
1996-08-02 17:04 Carlos Carvalho
1996-08-02 18:16 ` Zoltan Hidvegi
1996-08-02 18:19 ` Zoltan Hidvegi
1996-08-02 21:05 ` Carlos Carvalho
1996-08-02 19:21 ` Zoltan Hidvegi
1996-08-02 19:45 ` Zefram [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=19129.199608021945@stone.dcs.warwick.ac.uk \
--to=a.main@dcs.warwick.ac.uk \
--cc=carlos@riglos.fisica.ufpr.br \
--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).