From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 12089 invoked by alias); 13 Aug 2018 22:44:38 -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: 43290 Received: (qmail 16450 invoked by uid 1010); 13 Aug 2018 22:44:38 -0000 X-Qmail-Scanner-Diagnostics: from mail-io0-f175.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.223.175):SA:0(-1.9/5.0):. Processed in 1.226092 secs); 13 Aug 2018 22:44:38 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-1.9 required=5.0 tests=BAYES_00,RCVD_IN_DNSWL_NONE, SPF_PASS,T_DKIMWL_WL_MED,T_DKIM_INVALID autolearn=ham autolearn_force=no version=3.4.1 X-Envelope-From: dana@dana.is X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=dana-is.20150623.gappssmtp.com; s=20150623; h=mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=taz2xBZVgUni69OiPkcQdSDiEoDDJaFRdZDuLVZK/PQ=; b=JNJDShVMPrGYyEHZEBR2JFn4jjjiszS5fOHOK7FyOBlXy86JuuxERoioLOLZI5DvaG WfXFHLXeisOnYFpHRDkUO7jNeuOyIVNAQdpu8ulq1fR0jEFNnZVv3IRWr+RHhY2vX2Rs XyRQpFj8It/ozuP5AUrG1whnm8NrBXZ07LNohPrm1GnM1U/hnlgOYRFRDf+Lpy5H9xSV tyaet79UAurectLQCYvTYV54V5TZrHz9RubL6a8iOBVPcYf1Ey/NmdUQU6/+orPIC7UC xLZtIHboqhopeMEpgIai3fESd/jyhT+v/VzcRbcAZ4QLvDu6s/Mx1i7qBqhwPOelbEOA KERg== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20161025; h=x-gm-message-state:mime-version:subject:from:in-reply-to:date:cc :content-transfer-encoding:message-id:references:to; bh=taz2xBZVgUni69OiPkcQdSDiEoDDJaFRdZDuLVZK/PQ=; b=ggTZZPCaFk9MmHARpdEGQJ0JPAUT70YCfJfS+woOBnFD6pCQ7hBjXCVVGAr66mcOZP mwMSgO8TiNl/rrnmu+7J9LZ0NTRmYwEFKnOrCYDKD0oLBfEXBAT2b/ymSYugxZ+rtF/G Jwj/5V7OQfWvskK4Wk+9/lX7tQ1ulsbRMnJQvrDRrNnivXdrbc3+jnSwZ2C8nBtV1pXZ ELvbxqu10yZM6Gra5H1ij5++vdc9CQbcZHFmWKHCUj7K0RWoRYctkgR8YnL6SUe+AIX3 rwbZsYwCIXjf8cRn0V/kMFhMeGwsaoNs/Wf3CXqia7Tl/gj35iIN73bkOBo4r3FXaXvL JVOQ== X-Gm-Message-State: AOUpUlEKTrophez5SVM9FQCL44p6LOmvVbP9HIiYKfLumwhq3QGJCDQK nxXX9+l61CBlwv8GB+tJhroxkw== X-Google-Smtp-Source: AA+uWPwrsw2x811R1pR72VPTrSp/p0ei1B4q6LubcOx88r2lxCho3fTfTxWB/nTSG4D/dOH0BbRLEA== X-Received: by 2002:a6b:1b53:: with SMTP id b80-v6mr16053478iob.48.1534200274307; Mon, 13 Aug 2018 15:44:34 -0700 (PDT) Content-Type: text/plain; charset=utf-8 Mime-Version: 1.0 (Mac OS X Mail 11.4 \(3445.8.2\)) Subject: Re: "off by one fix in multiple prompts" breaks multiline prompt From: dana In-Reply-To: Date: Mon, 13 Aug 2018 17:44:32 -0500 Cc: Peter Stephenson , Guillaume Chazarain , "zsh-workers@zsh.org" , Warepire - Content-Transfer-Encoding: quoted-printable Message-Id: <8201EC10-DCE3-4E29-8B9A-C047E843153A@dana.is> References: <20180813084255eucas1p102bc21872ad72a2cd049d8d9db2f0e86~KZResIryo0309103091eucas1p10@eucas1p1.samsung.com> <20180813113640eucas1p19d52c9c05089626f375a00c5115aef32~KbpML4Mzp0510505105eucas1p1P@eucas1p1.samsung.com> <20180813125810eucas1p181a58cb55dc815863d6d81e1cd629d71~KcwV9B7ZD1627716277eucas1p1o@eucas1p1.samsung.com> <3F00E10A-6A65-4201-A4E2-2A29929111C1@dana.is> <383CC796-865C-4774-A9C2-AD44997784B4@dana.is> To: Bart Schaefer X-Mailer: Apple Mail (2.3445.8.2) On 13 Aug 2018, at 16:45, Bart Schaefer = wrote: >This is why for years we tried to limit everything to 1 column less >than the exact width. Oh, yeah :/ On 13 Aug 2018, at 16:45, Bart Schaefer = wrote: >Presumably ZLE_RPROMPT_INDENT=3D0 helps in that case? As far as i can tell, in Apple Terminal... ... when the check is > (as it is in the repo now), setting it to 0 = causes the editor to get lost as soon as i go past the last column. I think that's = the same behaviour Warepire found (can't remember in which terminal, but not = Apple's) when testing that setting at your suggestion before. ... when the check is >=3D (as it was before the previous change), = setting it to 0 makes no difference. In the case of the last line wrapping, it works as = expected either way, and in the case of a new-line after the last column, the = prompt swallows the preceding line of input either way. The change from >=3D to > seems bogus to me now =E2=80=94 it only works = by accident in that one case. As far as the new-line check, i'm not sure how to = determine if that's a good direction, besides just trying it in different terminals. = I can do that later if it's not completely disproven already. dana