Zsh Mailing List Archive Messages sorted by: Reverse Date, Date, Thread, Author

Re: alwayslastprompt problem

X-seq: zsh-workers 18201
From: gak@xxxxxxxxxxxxxx (Greg Klanderman)
To: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
Subject: Re: alwayslastprompt problem
Date: Wed, 5 Feb 2003 14:38:30 -0500 (EST)
Cc: zsh-workers@xxxxxxxxxx (Zsh list)
In-reply-to: <1030205161536.ZM22234@xxxxxxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <15934.59328.619062.393204@xxxxxxxxxxxxxxxxxxx> <1030204025755.ZM15281@xxxxxxxxxxxxxxxxxxxxxxx> <15935.16623.823108.734629@xxxxxxxxxxxxxxxxxxx> <1030205161536.ZM22234@xxxxxxxxxxxxxxxxxxxxxxx>
Reply-to: gak@xxxxxxxxxxxxxx

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 <schaefer@xxxxxxxxxxxxxxxx> 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.

References:
- alwayslastprompt problem
  - From: Greg Klanderman
- Re: alwayslastprompt problem
  - From: Bart Schaefer
- Re: alwayslastprompt problem
  - From: Greg Klanderman
- Re: alwayslastprompt problem
  - From: Bart Schaefer

Messages sorted by: Reverse Date, Date, Thread, Author