zsh-workers
 help / color / mirror / code / Atom feed
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
To: Millian Poquet <millian.poquet@irit.fr>
Cc: zsh-workers@zsh.org
Subject: Re: [bug report] prompt can erase messages written on the terminal by background processes
Date: Wed, 7 Dec 2022 23:55:17 +0100	[thread overview]
Message-ID: <CAN=4vMq2kc1cSV_0N-c6o32C3UR3hVSjE3mF+kV4pjcy7YR9=g@mail.gmail.com> (raw)
In-Reply-To: <9e3026aa-39a1-dd50-4d29-a64724d4eaaf@irit.fr>

On Wed, Dec 7, 2022 at 8:04 PM Millian Poquet <millian.poquet@irit.fr> wrote:
>
> prompt can erase messages written on the terminal by background processes

Not just prompt but zle in general, or any program really that moves
the cursor (try `top`, for example, or `less`). There is no way around
it. Zle assumes that nobody else prints to the terminal. If this
assumption is violated, the outcome is unspecified mess.

Here's a simpler demonstration. Run this in interactive zsh:

  ( sleep 3; print -rn hello ) &!

Then immediately type "ls" and wait without hitting enter. A moment
later "hello" will appear on the command line. Try editing it and
observe that zle is essentially broken.

You can break any terminal program that moves the cursor by using this
trick. Try running `top` immediately after the command listed above,
or after you C program, which is essentially the same.

Roman.


  reply	other threads:[~2022-12-07 22:56 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 [this message]
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

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='CAN=4vMq2kc1cSV_0N-c6o32C3UR3hVSjE3mF+kV4pjcy7YR9=g@mail.gmail.com' \
    --to=roman.perepelitsa@gmail.com \
    --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).