From: Oliver Kiddle <opk@zsh.org>
To: Millian Poquet <millian.poquet@irit.fr>, zsh-workers@zsh.org
Subject: Re: [bug report] prompt can erase messages written on the terminal by background processes
Date: Thu, 08 Dec 2022 16:03:07 +0100 [thread overview]
Message-ID: <39468-1670511787.350409@tM9p.ctXg.8m2T> (raw)
In-Reply-To: <CAH+w=7aDn7SCv4Bao7ZQqtUaEv8EkvBXa15kM_nkF_GHLAcSFg@mail.gmail.com>
Bart Schaefer wrote:
> > There is no way around it. Zle assumes that nobody else prints to the terminal.
>
> Perhaps try this.
>
> get_cursor_pos() {
> print -n $'\e[6n'
> IFS=$'\e[;' read -s -d R -A ${1:-reply}
Aside from only working if the timing of the background process involves
writing to the terminal before the prompt is printed this approach also
has another disadvantage: the read can swallow any text that has been
typed before it prints the prompt. To see that, run something like sleep
3 and type your next command while it sleeps.
I've used a similar approach as a fallback mechanism[1] to detect a dark or
light background by printing '\e]11;?\a'. Typeahead is rarer for a new
window but I did add handling to try to grab the typeahead and restore
it with print -z but it still gets messed up occasionally; and I can't
be sure that all the typeahead was intended for zsh.
It might be better to report a bug for whatever programme you have that
forks and continues to write to the terminal from the child process
while the parent quits.
Oliver
[1] The primary mechanism is to look at $COLORFGBG which I typically add
to the list of variables that ssh/sshd will pass/accept.
prev parent reply other threads:[~2022-12-08 15:03 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-12-07 19:02 Millian Poquet
2022-12-07 22:55 ` Roman Perepelitsa
2022-12-08 3:46 ` Bart Schaefer
2022-12-08 8:21 ` Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes) Stephane Chazelas
2022-12-08 8:34 ` Roman Perepelitsa
2022-12-08 10:02 ` Stephane Chazelas
2022-12-08 10:10 ` Stephane Chazelas
2022-12-08 10:19 ` Mikael Magnusson
2022-12-09 2:19 ` Bart Schaefer
2022-12-09 12:46 ` Philippe Altherr
2022-12-10 4:30 ` Bart Schaefer
2022-12-10 14:55 ` Private variables not private enough? (Was: Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes)) Philippe Altherr
2022-12-10 17:36 ` Bart Schaefer
2022-12-10 20:38 ` Bart Schaefer
2022-12-11 18:00 ` Get cursor position (Was: [bug report] prompt can erase messages written on the terminal by background processes) Stephane Chazelas
2022-12-09 1:39 ` Bart Schaefer
2022-12-08 8:45 ` [bug report] prompt can erase messages written on the terminal by background processes Roman Perepelitsa
2022-12-08 15:03 ` Oliver Kiddle [this message]
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=39468-1670511787.350409@tM9p.ctXg.8m2T \
--to=opk@zsh.org \
--cc=millian.poquet@irit.fr \
--cc=zsh-workers@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).