From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21543 invoked from network); 2 Dec 1996 17:40:15 -0000 Received: from euclid.skiles.gatech.edu (list@130.207.146.50) by coral.primenet.com.au with SMTP; 2 Dec 1996 17:40:15 -0000 Received: (from list@localhost) by euclid.skiles.gatech.edu (8.7.3/8.7.3) id MAA20064; Mon, 2 Dec 1996 12:14:58 -0500 (EST) Resent-Date: Mon, 2 Dec 1996 12:14:58 -0500 (EST) From: Zefram Message-Id: <9935.199612021714@stone.dcs.warwick.ac.uk> Subject: Re: hashinfo improvement To: hzoli@cs.elte.hu (Zoltan Hidvegi) Date: Mon, 2 Dec 1996 17:14:52 +0000 (GMT) Cc: zefram@dcs.warwick.ac.uk, zsh-workers@math.gatech.edu In-Reply-To: <199612021659.RAA07905@bolyai.cs.elte.hu> from "Zoltan Hidvegi" at Dec 2, 96 05:59:03 pm X-Loop: zefram@dcs.warwick.ac.uk X-Stardate: [-31]8513.59 X-US-Congress: Moronic fuckers Content-Type: text Resent-Message-ID: <"toqjC2.0.Qv4.Hwmeo"@euclid> Resent-From: zsh-workers@math.gatech.edu X-Mailing-List: archive/latest/2519 X-Loop: zsh-workers@math.gatech.edu Precedence: list Resent-Sender: zsh-workers-request@math.gatech.edu >I have started to implement autoloadable zle. Excellent. I'd been planning to do that myself. > It may be worth to not set the ZLE option by >default when invoking zsh as sh. This may be desirable when zsh is /bin/sh >and the zle modules are not on the root filesystem. Probably a good idea. What happens if the ZLE module can't be loaded? The way I was going to implement it, zsh would fall back on a trivial routine that outputs a simple fixed prompt and reads from the tty in cooked mode. -zefram