From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5461 invoked from network); 5 Feb 2003 19:40:55 -0000 Received: from sunsite.dk (130.225.247.90) by ns1.primenet.com.au with SMTP; 5 Feb 2003 19:40:55 -0000 Received: (qmail 15085 invoked by alias); 5 Feb 2003 19:39:46 -0000 Mailing-List: contact zsh-workers-help@sunsite.dk; run by ezmlm Precedence: bulk X-No-Archive: yes X-Seq: 18201 Received: (qmail 15070 invoked from network); 5 Feb 2003 19:39:46 -0000 Received: from localhost (HELO sunsite.dk) (127.0.0.1) by localhost with SMTP; 5 Feb 2003 19:39:46 -0000 X-MessageWall-Score: 0 (sunsite.dk) Received: from [63.107.91.101] by sunsite.dk (MessageWall 1.0.8) with SMTP; 5 Feb 2003 19:39:44 -0000 Received: from itasoftware.com (phl.internal.itasoftware.com [192.168.1.115]) by mta.internal.itasoftware.com (8.12.6/8.12.6) with ESMTP id h15JcVxY007280; Wed, 5 Feb 2003 14:38:31 -0500 Received: (from greg@localhost) by itasoftware.com (8.9.3/8.8.7) id OAA27030; Wed, 5 Feb 2003 14:38:30 -0500 Message-ID: <15937.26678.694562.670071@phl.itasoftware.com> Date: Wed, 5 Feb 2003 14:38:30 -0500 (EST) From: gak@klanderman.net (Greg Klanderman) To: "Bart Schaefer" Cc: zsh-workers@sunsite.dk (Zsh list) Subject: Re: alwayslastprompt problem In-Reply-To: <1030205161536.ZM22234@candle.brasslantern.com> References: <15934.59328.619062.393204@phl.itasoftware.com> <1030204025755.ZM15281@candle.brasslantern.com> <15935.16623.823108.734629@phl.itasoftware.com> <1030205161536.ZM22234@candle.brasslantern.com> Reply-To: gak@klanderman.net X-Mailer: VM 6.62 under 21.1 (patch 9) "Canyonlands" XEmacs Lucid Mime-Version: 1.0 (generated by tm-edit 7.108) Content-Type: text/plain; charset=US-ASCII Interesting.. if you haven't figured it out I'll probably look into this sometime but not for at least a week or two. greg >>>>> Bart Schaefer writes: > On Feb 3, 11:26pm, Greg Klanderman wrote: > } > } Is there any reason zsh couldn't handle alwayslastprompt in this > } situation? > It appears to be an order-of-initialization issue. In a non-interactive > shell, the terminal isn't set up until vared is actually invoked, and > for some reason that causes the ZLE refresh routines to believe that it > isn't possible to do alwayslastprompt. > I haven't figured out exactly what is different in the two cases.