From mboxrd@z Thu Jan 1 00:00:00 1970 Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by melb.werple.net.au (8.7.5/8.7.3/2) with ESMTP id SAA05166 for ; Wed, 24 Jul 1996 18:55:11 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id EAA06153; Wed, 24 Jul 1996 04:50:22 -0400 (EDT) Resent-Date: Wed, 24 Jul 1996 04:50:22 -0400 (EDT) From: Zefram Message-Id: <13479.199607240831@stone.dcs.warwick.ac.uk> Subject: Re: False alarm (nonomatch and cshnullglob) To: schaefer@nbn.com Date: Wed, 24 Jul 1996 09:31:48 +0100 (BST) Cc: zsh-workers@math.gatech.edu In-Reply-To: <960723145813.ZM3415@candle.brasslantern.com> from "Bart Schaefer" at Jul 23, 96 02:58:13 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]7856.77 X-US-Congress: Moronic fuckers MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"M3MTY2.0.0W1.DFUzn"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/1752 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >I should have mentioned that this implementation is not suitable for use >in combination with "setopt localoptions" in shell functions. If you >use this wrapper, then your shell functions that desire localoptions need >to always use "builtin setopt". > >Having the behavior itself built in to zsh would eliminate that problem. ...but would introduce the problem that an innocent setopt can change more options than it appears to, confusing lots of existing functions. If we introduce group option setting, it must be using new option names, to avoid changing the meaning of existing options.