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

Re: alwayslastprompt problem

X-seq: zsh-workers 18200
From: "Bart Schaefer" <schaefer@xxxxxxxxxxxxxxxx>
To: gak@xxxxxxxxxxxxxx, zsh-workers@xxxxxxxxxx (Zsh list)
Subject: Re: alwayslastprompt problem
Date: Wed, 5 Feb 2003 16:15:36 +0000
In-reply-to: <15935.16623.823108.734629@xxxxxxxxxxxxxxxxxxx>
Mailing-list: contact zsh-workers-help@xxxxxxxxxx; run by ezmlm
References: <15934.59328.619062.393204@xxxxxxxxxxxxxxxxxxx> <1030204025755.ZM15281@xxxxxxxxxxxxxxxxxxxxxxx> <15935.16623.823108.734629@xxxxxxxxxxxxxxxxxxx>

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.

Follow-Ups:
- Re: alwayslastprompt problem
  - From: Greg Klanderman

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

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