From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 5568 invoked by alias); 13 Jul 2016 17:11: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: X-Seq: 38848 Received: (qmail 4625 invoked from network); 13 Jul 2016 17:11:38 -0000 X-Qmail-Scanner-Diagnostics: from mailout3.w1.samsung.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(210.118.77.13):SA:0(-1.3/5.0):. Processed in 0.120292 secs); 13 Jul 2016 17:11: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.3 required=5.0 tests=RP_MATCHES_RCVD autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: p.stephenson@samsung.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at samsung.com does not designate permitted sender hosts) X-AuditID: cbfec7f5-f792a6d000001302-a1-578673e92361 Date: Wed, 13 Jul 2016 18:01:26 +0100 From: Peter Stephenson To: zsh-workers@zsh.org Subject: Re: State of the ZLE region across new prompts Message-id: <20160713180126.046dff19@pwslap01u.europe.root.pri> In-reply-to: <160713093819.ZM21122@torch.brasslantern.com> References: <160711212814.ZM15416@torch.brasslantern.com> <53283.1468404826@hydra.kiddle.eu> <160713093819.ZM21122@torch.brasslantern.com> Organization: Samsung Cambridge Solution Centre X-Mailer: Claws Mail 3.7.9 (GTK+ 2.22.0; i386-redhat-linux-gnu) MIME-version: 1.0 Content-type: text/plain; charset=US-ASCII Content-transfer-encoding: 7bit X-Brightmail-Tracker: H4sIAAAAAAAAA+NgFrrALMWRmVeSWpSXmKPExsVy+t/xa7ovi9vCDZo+i1kcbH7I5MDoserg B6YAxigum5TUnMyy1CJ9uwSujIe/jrMVtLJUXDq8iamBcSZzFyMnh4SAicT1SetZIGwxiQv3 1rN1MXJxCAksZZSYfv4ZK4Qzg0li4ZXzjBDOOUaJhskTmSGcs4wSu/cfBHI4OFgEVCXWLpMB GcUmYCgxddNsRhBbREBc4uza82ArhAXMJR69+McOYvMK2EssuvaTCaSVU8BKYvpsPYiRfYwS 3QfOgJ3HL6AvcfXvJyaI8+wlZl45wwjRKyjxY/I9sJnMAloSm7c1sULY8hKb17wF6xUSUJe4 cXc3+wRG4VlIWmYhaZmFpGUBI/MqRtHU0uSC4qT0XCO94sTc4tK8dL3k/NxNjJBw/rqDcekx q0OMAhyMSjy8D/LawoVYE8uKK3MPMUpwMCuJ8K4vAgrxpiRWVqUW5ccXleakFh9ilOZgURLn nbnrfYiQQHpiSWp2ampBahFMlomDU6qBMfbHkVWTNkz8y7V9aUNMjk278Z5JundWF3B+OPjE VaX7b+Yxzde5LP+/dy5w4Ko7trldWvqO9cFQHo/5jZ98DizJ0twUGn+jv2550/I/3Fml6s9Z zV4Jx19b4xPN3fdNmW1yw/9Nj/bG/Ntdvk5GV+Bcr+2uFwxT501K0p63PfXO4wfzXnXwxiix FGckGmoxFxUnAgDw+NQgYwIAAA== On Wed, 13 Jul 2016 09:38:19 -0700 Bart Schaefer wrote: > On Jul 13, 12:13pm, Oliver Kiddle wrote: > } > } Yes, the region is remaining active. We reset it before calling > } zle-line-finish. The patch below instead resets it on entry, before > } zle-line-init. > > Peter seemed to think it might be necessary to reset it in both places? I don't actually know of a case where resetting it on exit, too, is going to add to the further spreading of joy and contentment. pws