From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: X-Spam-Checker-Version: SpamAssassin 3.4.2 (2018-09-13) on inbox.vuxu.org X-Spam-Level: X-Spam-Status: No, score=-1.1 required=5.0 tests=DKIM_SIGNED,DKIM_VALID, DKIM_VALID_AU,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 9078653c for ; Thu, 18 Apr 2019 18:57:17 +0000 (UTC) Received: (qmail 15853 invoked by alias); 18 Apr 2019 18:57:04 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: List-Unsubscribe: X-Seq: 44233 Received: (qmail 8496 invoked by uid 1010); 18 Apr 2019 18:57:04 -0000 X-Qmail-Scanner-Diagnostics: from mail-io1-f42.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.101.1/25419. spamassassin: 3.4.2. Clear:RC:0(209.85.166.42):SA:0(-2.0/5.0):. Processed in 1.008657 secs); 18 Apr 2019 18:57:04 -0000 X-Envelope-From: mikachu@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.42 as permitted sender) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20161025; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=5WYUM8YAQ0qAQIVebS2A+UfaC5Qr4HhwqLywT+6VjXg=; b=YGnjIES5iiUCpfDG12hls8auMCjCVhKZ0Pmvg2958f3RqWqkovgD3jzc/uANqiAFc3 zY1+PBlZZXXKs2nNPKOVBo580UPsWfRbcskbS52J5mHzJAgqbJZTApwybQLwb3hZIFsh aNF6VyCv+ffvQLkPvpDRleGeUpr+D2DHOcAL8aF5lx7NrZ22MvDroakr1c+9a3UQhB/J Kx22zBvIBMndll9Zmy3lIhPuhz0tfPpDQQy85wU45dztYXsX1cxMvH1xRvh9kwcCTcYx 7YjCU84fF3o2ijM26UVMCXqpk1JpbuF4PToKFKnlJjGQQHKmOkUz08yr9D59wMukJ2i9 hgLQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:in-reply-to:references:from:date :message-id:subject:to:cc; bh=5WYUM8YAQ0qAQIVebS2A+UfaC5Qr4HhwqLywT+6VjXg=; b=h024JbP0KcYHFLrQFCKh0YkSyKbux7kvx2jtbzxdVApDpy7FdFuEUtcZ0o61EctCg3 HA2k8/IYxg8mTXUqQ39WrLmi5Kce8TjKKwYDk4kM/lWZYBMngbHkGwhhtg+NNz/5VOFF Iu7Q6WNlP1DSkSixK4NieTKCYVouNROds9Tjgo9Frj2ROQ/6S+hGRBIsiJqmyoJaskXC RgXAA94oz/EvtMQ8WWTFy9DGS698CoOG7196aEfJ/JDzJS14N5g07aR0qMy5bJVlFGH5 eQ9L662BAIWFxpCFozUrMvHLaZeun1hD0AoBlrtmwFUJIfaVk7KaPIdg02d2wTxlfgAJ 89PQ== X-Gm-Message-State: APjAAAUC6nd54RXrt85jCUv5YqzgRVUQHRmwtU0T2F5FhmPWoMvoUIfz XNREePvKq4yoUFKobNHiC4h9uXrHv8HN3CHTwmU= X-Google-Smtp-Source: APXvYqwh6Mo1JP2F2RsJP05faFC0R+iZmGzXDFLwubiLvv8dkLaW3Qy1qfUfzYQJCafuBxVn8fVvETfgosCW4zvnRVo= X-Received: by 2002:a5e:d505:: with SMTP id e5mr40914861iom.189.1555613790361; Thu, 18 Apr 2019 11:56:30 -0700 (PDT) MIME-Version: 1.0 In-Reply-To: References: <8B423652-107C-4DDA-A333-907B42A670F8@dana.is> From: Mikael Magnusson Date: Thu, 18 Apr 2019 20:56:29 +0200 Message-ID: Subject: Re: Misaligned cursor when prompt linebroken To: dana Cc: Zsh hackers list Content-Type: text/plain; charset="UTF-8" On 4/18/19, Mikael Magnusson wrote: > On 4/18/19, Mikael Magnusson wrote: >> On 4/18/19, dana wrote: >>> On 18 Apr 2019, at 10:39, Mikael Magnusson wrote: >>>>PS1=${(l:$COLUMNS::a:)}b >>>>the cursor is placed on top of the "b" for me, both in urxvt and >>>>xterm. Under zsh -f the initial rendering appears correct, but not >>>>after I type two characters >>> >>> Same for me in Terminal.app. The return of workers/43267 (&al.), i >>> suppose? >> >> Just a small additional note that it doesn't matter that it's only one >> character extra in my example, the same thing happens if you put >> bbbbbbbb instead of just b. > > I tried reverting that commit (w/42285) and it fixes my problem. I > also can't reproduce any behavior that erases lines with it reverted. > Since having the commit breaks all prompts that are longer than one > line in many(?) terminals, and only fixes the case where it is exactly > as long as one line in some(?) terminals, I would argue for reverting > it in git. Dana pointed me more specifically to w/43288 on IRC which was reportedly committed a while ago but not actually. I checked that it fixes my case too and doesn't seem to break w/42285, so I've committed it (actually). -- Mikael Magnusson