From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-users-return-17796-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 29977 invoked by alias); 29 Apr 2013 08:57:10 -0000
Mailing-List: contact zsh-users-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Users List <zsh-users.zsh.org>
List-Post: <mailto:zsh-users@zsh.org>
List-Help: <mailto:zsh-users-help@zsh.org>
X-Seq: 17796
Received: (qmail 26477 invoked from network); 29 Apr 2013 08:57:07 -0000
X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au
X-Spam-Level: 
X-Spam-Status: No, score=-6.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_HI,
	SPF_HELO_PASS autolearn=ham version=3.3.2
Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts)
X-AuditID: cbfec7f5-b7fa36d000007f20-d5-517e3385535a
Date: Mon, 29 Apr 2013 09:47:00 +0100
From: Peter Stephenson <p.stephenson@samsung.com>
To: Russell Harmon <russ@eatnumber1.com>, zsh-users@zsh.org
Subject: Re: Augmenting a Sticky Emulation Mode
Message-id: <20130429094700.6c8db4a9@pwslap01u.europe.root.pri>
In-reply-to:
 <CA+zrezTCVO58URokScwT45VHa_MkgpvnEuNbvzB+Uk97+WpQRQ@mail.gmail.com>
References:
 <CA+zrezRfVDfTHYMMj2HpeyrUJvyuTQ=p+PL0tV6u3hcZ1nOfAw@mail.gmail.com>
 <130426180127.ZM18989@torch.brasslantern.com>
 <CA+zrezROkjsD5mum5TCZ02h5Z+MTWiHC59cyuAyt1J0xpgUG+g@mail.gmail.com>
 <CA+zrezTCVO58URokScwT45VHa_MkgpvnEuNbvzB+Uk97+WpQRQ@mail.gmail.com>
Organization: Samsung Cambridge Solution Centre
X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu)
MIME-version: 1.0
Content-type: text/plain; charset=US-ASCII
Content-transfer-encoding: 7bit
X-Brightmail-Tracker:
 H4sIAAAAAAAAA+NgFprGLMWRmVeSWpSXmKPExsVy+t/xa7qtxnWBBgcv6lic37CQ1WLHyZWM
	Dkwelw6sYfRYdfADUwBTFJdNSmpOZllqkb5dAlfG7xmPWAuus1ZMXzePrYFxL0sXIweHhICJ
	xOpV0V2MnECmmMSFe+vZuhi5OIQEljJKbH36mxnC6WeSWLzzFxtIFYuAqsS55vuMIDabgKHE
	1E2zwWwRAWuJBZNPgA0VFtCXuL2EFyTMK2Av8fvhLmYQm1MgWOLM2R3sEDMnMEncbW1mB0nw
	A9Vf/fuJCeIKe4mZV84wQjQLSvyYfI8FxGYW0JLYvK2JFcKWl9i85i3zBEaBWUjKZiEpm4Wk
	bAEj8ypG0dTS5ILipPRcI73ixNzi0rx0veT83E2MkLD8uoNx6TGrQ4wCHIxKPLyBm2sDhVgT
	y4orcw8xSnAwK4nwKhrVBQrxpiRWVqUW5ccXleakFh9iZOLglGpgTOTV3KhsrVW6asHL5VFv
	qyxkrt//IWo9/3Lzxs/VOvlvnfx99zSzKhRMf9DXWTjhWk3U+4yls37Pmr4wx7/ybJbJCam5
	F2oKWXhsz34LVHnSdPHKgr5Xy8Xu7XF55P7Y/jvv0S/tLb3qU29Gbb5gsj6+XdjV1OZ+RqBU
	olMRLxtbjJKB4L5LSizFGYmGWsxFxYkA6SBzDykCAAA=

On Sun, 28 Apr 2013 22:44:17 -0700
Russell Harmon <russ@eatnumber1.com> wrote:
> I'm also a little confused here.
> 
> emulate -R sh -o noshglob -c 'foo() {; setopt; }'; foo
> enables MAIL_WARNING while
> emulate -R sh -o shglob -c 'foo() {; setopt; }'; foo
> fails to enable shglob

Something *is* a bit wacky here, maybe not what you're seeing...
You need the zsh/parameter module loaded, which it probably will be for
completion.

% emulate -R sh -o noshglob -c 'foo() { print ${options[shglob]}; }'; foo
on
% emulate -R sh +o shglob -c 'foo() { print ${options[shglob]}; }'; foo
off

I can't think of any good reason why they should be different, though
maybe it'll occur to me if I look deeper.

pws