From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: zsh-workers-request@euclid.skiles.gatech.edu Received: from euclid.skiles.gatech.edu (list@euclid.skiles.gatech.edu [130.207.146.50]) by coral.primenet.com.au (8.7.5/8.7.3) with ESMTP id XAA18941 for ; Wed, 9 Oct 1996 23:43:10 +1000 (EST) Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id JAA14112; Wed, 9 Oct 1996 09:19:31 -0400 (EDT) Resent-Date: Wed, 9 Oct 1996 09:19:31 -0400 (EDT) From: Zefram Message-Id: <29668.199610091318@stone.dcs.warwick.ac.uk> Subject: Re: alias -x? To: zsh-workers@math.gatech.edu (Z Shell workers mailing list) Date: Wed, 9 Oct 1996 14:18:48 +0100 (BST) In-Reply-To: <199610091129.NAA26517@hydra.ifh.de> from "Peter Stephenson" at Oct 9, 96 01:29:14 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]8242.77 X-US-Congress: Moronic fuckers MIME-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Content-Transfer-Encoding: 7bit Resent-Message-ID: <"ndb4w.0.QS3.TPwMo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2209 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu > (Maybe Zefram could handle code to deal with >options like `emacs', `nolog', `vi', `viraw' and `trackall' quite >easily with the rewritten option code.) It's not quite that simple. When I can find some free time (ha!) I have plans for another option patch, that was delayed by the release of 3.0. Addition of options like `emacs' might be part of that, but what should `[[ -o emacs ]]' do? (I do have a reasonable answer, but my point is that the semantics are inevitably non-obvious.) Zoltan, are you planning to release a 3.1 to which we can add features? -zefram