From: Grant Taylor <gtaylor@tnetconsulting.net>
To: zsh-users@zsh.org
Subject: Re: Why does zsh clear to end-of-screen after prompt?
Date: Sun, 27 Aug 2023 10:36:17 -0500 [thread overview]
Message-ID: <6fc464c1-1128-0747-1536-9065a60ced6e@tnetconsulting.net> (raw)
In-Reply-To: <CAN=4vMr+yDCrgLzfK-WqTLjR1hHQfNQfC91qOCcrCPb_Ocra=A@mail.gmail.com>
On 8/27/23 3:34 AM, Roman Perepelitsa wrote:
> An alternative solution is to embed the info in PROMPT. In order to
> avoid wasting 20 lines of the TTY real estate on each command, you can
> automatically contract the prompt before executing each command. Thus,
> if you run `pwd` twice in a row, your TTY might look like this:
>
> me@box ~ % pwd
> /home/me
> me@box ~ % pwd
> /home/me
>
> foo=bar
> baz=qux
> me@box ~ % █
>
> In this approach the extra info ("foo=bar", etc.) is always displayed
> right above the current prompt. This is basically Transient Prompt
> from Powerlevel10k
> (https://raw.githubusercontent.com/romkatv/powerlevel10k-media/master/transient-prompt.gif)
> but with a fatter prompt.
This looks like it might do something I've been contemplating doing.
Having a prompt that is multiple lines but not taking up that screen
real estate in history.
I need to reverse engineer this and adapt it to what I want to do.
I'd simply like a multi-line prompt that includes:
- A separation line from the rest of the screen, blank or repeating
sequence is fine.
- A line that includes path and similar things.
- The actual command entry line.
I already have transient RPROMPT.
Time to read & understand what is happening. :-)
Grant. . . .
next prev parent reply other threads:[~2023-08-27 15:37 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-25 19:52 John Hawkinson
2023-08-26 0:18 ` Bart Schaefer
2023-08-26 0:59 ` John Hawkinson
2023-08-26 1:39 ` Bart Schaefer
2023-08-27 8:34 ` Roman Perepelitsa
2023-08-27 15:36 ` Grant Taylor [this message]
2023-08-27 16:02 ` Roman Perepelitsa
2023-08-27 18:55 ` Grant Taylor
2023-09-09 23:23 ` Bart Schaefer
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=6fc464c1-1128-0747-1536-9065a60ced6e@tnetconsulting.net \
--to=gtaylor@tnetconsulting.net \
--cc=zsh-users@zsh.org \
/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).