From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-45370-ml=inbox.vuxu.org@zsh.org>
X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org
X-Spam-Level: 
X-Spam-Status: No, score=-1.0 required=5.0 tests=DKIM_ADSP_CUSTOM_MED,
	FREEMAIL_FROM,MAILING_LIST_MULTI,RCVD_IN_DNSWL_NONE autolearn=ham
	autolearn_force=no version=3.4.2
Received: from primenet.com.au (ns1.primenet.com.au [203.24.36.2])
	by inbox.vuxu.org (OpenSMTPD) with ESMTP id 569e4088
	for <ml@inbox.vuxu.org>;
	Sat, 1 Feb 2020 17:23:04 +0000 (UTC)
Received: (qmail 8636 invoked by alias); 1 Feb 2020 17:22:54 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
List-Unsubscribe: <mailto:zsh-workers-unsubscribe@zsh.org>
X-Seq: 45370
Received: (qmail 13892 invoked by uid 1010); 1 Feb 2020 17:22:54 -0000
X-Qmail-Scanner-Diagnostics: from mail-io1-f54.google.com by f.primenet.com.au (envelope-from <roman.perepelitsa@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.102.1/25703. spamassassin: 3.4.2.  
 Clear:RC:0(209.85.166.54):SA:0(-2.0/5.0):. 
 Processed in 1.348305 secs); 01 Feb 2020 17:22:54 -0000
X-Envelope-From: roman.perepelitsa@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.166.54 as permitted sender)
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20161025;
        h=x-gm-message-state:mime-version:references:in-reply-to:from:date
         :message-id:subject:to:cc;
        bh=fEo3uGwAPF3qU/P6ugGuaN3UdM80v96xL7dPGURqtgc=;
        b=dmL/kysLPJBOfyteRqO3f5cbBQVLQqe0O6zdI7LKY188ucRFNCfHKWld3wdMtM6XMO
         acTiwDrcElAWUEdHelcl0Qx8Z/6lBv8Ocjxjj0pki+8UgKIMendNP+nDxzv2eq9nSnba
         4+4t1/Icr584eBu4dRm28a5A+GlAYWsapLd8q9PWR+eKtctY7PixUzed3B5ib+pani+M
         QeCCarL+ebk9JI8Aq/NHSL2yHTbKnYp1cA8hjYI47kJj4VQmbcWE7d7sQ9/TqE1TpbnU
         cXdiL3nI/wwanb/5Yp7meBPeMzA56Hgp3OxfHYptGYBIu0v5zEYsgekkQsglV6kmhnFa
         30NQ==
X-Gm-Message-State: APjAAAVdDuW58vFqRrBJ46aVHI8IQHW0noG7zC6Ie89HXVV5TPeVCYd8
	8I9C2tSc5NGItCRPafjC6YyDL5Soeg0UIeg2jaDBBJhv
X-Google-Smtp-Source: APXvYqwFynMPZfYI5jZ3yqDj60D5qnxqVwz2DV46ztInWhXj3MOgAROl2A0ypvGJYMAcYS0cvO94bUSxz0cMGwOX+2w=
X-Received: by 2002:a05:6602:210a:: with SMTP id x10mr12892807iox.151.1580577739425;
 Sat, 01 Feb 2020 09:22:19 -0800 (PST)
MIME-Version: 1.0
References: <CAN=4vMp+E7esA48bEtRs-+Rmm9ng7i+FayGVqcLZqyjwVkayAw@mail.gmail.com>
 <CAKc7PVBEBDvmoxPNgPJUHK8wn2U-9cSNcdr0ADTumV_pu_D2Ww@mail.gmail.com>
 <CAN=4vMpWxg_-OLRSOYu+JcAnpuvdUp+k+7HVtPH9sXtEFiVh8g@mail.gmail.com>
 <CAKc7PVCBoLWhNMVdQGmmgFB_zaObo2Ga=YU21yWJC-6KZ+EsHQ@mail.gmail.com>
 <CAN=4vMpw1EEQHyhx2dAVN8cZ78SMy6-xmWFM1tRX8TDtsTN-fw@mail.gmail.com>
 <CAKc7PVB1Zmhv6JsLzVVUgSr6Yzyt8O9+Zr7tg3RUS1NfTkY+Mg@mail.gmail.com>
 <CAH+w=7ahPsMBEEXm-mgQnQpA6tnCpZzL77njcnqk72dkGzARJA@mail.gmail.com> <CAN=4vMq_Vx8hb4uTNTXaUgiM0aHS0ZnC4-ZSe7XR6VPqqwuMDg@mail.gmail.com>
In-Reply-To: <CAN=4vMq_Vx8hb4uTNTXaUgiM0aHS0ZnC4-ZSe7XR6VPqqwuMDg@mail.gmail.com>
From: Roman Perepelitsa <roman.perepelitsa@gmail.com>
Date: Sat, 1 Feb 2020 18:22:08 +0100
Message-ID: <CAN=4vMpAQkASWa1g60srrXj8EK3S_PZhb764yi-dYAqU9UquhQ@mail.gmail.com>
Subject: Re: PATCH: draw prompt on the correct line after window change
To: Bart Schaefer <schaefer@brasslantern.com>
Cc: Sebastian Gniazdowski <sgniazdowski@gmail.com>, Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset="UTF-8"

On Mon, Jan 6, 2020 at 8:38 PM Roman Perepelitsa
<roman.perepelitsa@gmail.com> wrote:
>
> On Mon, Jan 6, 2020 at 8:28 PM Bart Schaefer <schaefer@brasslantern.com> wrote:
> > IIR the problem correctly, a possible approach to resolve my concern would be to have the terminal report the cursor position for the shell to read+save it, rather than rely on the terminal save/restore action.
>
> I implemented this prior to the patch I sent. Unfortunately, this
> added enough prompt latency to make it noticeable.

I've implemented this again to verify that my recollection of the
reason I rejected this approach was correct. It was not. u7 is indeed
slow but the primary reason I abandoned it in the first implementation
is that it doesn't work here. The absolute position of prompt start
changes when terminal content gets reflown upon resize.

After a few more issues filed against powerlevel10k due to the
resizing bug, I wrote this troubleshooting entry:
https://github.com/romkatv/powerlevel10k/blob/master/README.md#horrific-mess-when-resizing-terminal-window.
Perhaps it'll help others who stumble on this.

Roman.