From: "Bart Schaefer" <schaefer@brasslantern.com>
To: gak@klanderman.net, zsh-workers@sunsite.dk (Zsh list)
Subject: Re: alwayslastprompt problem
Date: Wed, 5 Feb 2003 16:15:36 +0000 [thread overview]
Message-ID: <1030205161536.ZM22234@candle.brasslantern.com> (raw)
In-Reply-To: <15935.16623.823108.734629@phl.itasoftware.com>
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.
next prev parent reply other threads:[~2003-02-05 16:15 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2003-02-03 22:05 Greg Klanderman
2003-02-04 2:57 ` Bart Schaefer
2003-02-04 4:26 ` Greg Klanderman
2003-02-05 16:15 ` Bart Schaefer [this message]
2003-02-05 19:38 ` Greg Klanderman
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=1030205161536.ZM22234@candle.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=gak@klanderman.net \
--cc=zsh-workers@sunsite.dk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).