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-Qmail-Scanner-Diagnostics: from mail-pa0-f51.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.220.51):SA:0(0.0/5.0):. Processed in 0.107363 secs); 13 Jul 2016 16:38:00 -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=0.0 required=5.0 tests=T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=brasslantern-com.20150623.gappssmtp.com; s=20150623; h=from:message-id:date:in-reply-to:comments:references:to:subject :mime-version; bh=JnI85gU6YQeNUNPXgYWoWQofjPEjOaI6yGnRM+D46Hs=; b=ijjxxhoCWT3tcQyftG2cMyHTEifm/aPvq8LTX7TmyJHzQ0YFYYE6YGkDcnCKIMqKn5 VLBs6jl65Bag+CWPQlIF7eZVa/CMUZuOZKdbBhUR5YliRPb1htJmHbstIJJQqm5hGNNz 7XfMxcPxZUR19hOqfz8if5+MiOJNsyuJ53VR7xayn+DJogH1Ka6aJNYRnciWECo4or6P N66eF5V++02MGuHlF2vTuNIv2PlA28WYlC1IGH34RkFi6I82dwtYhM5SkjoK8NV7O8Pz menkCuPQOmBCNnjBVW8ElVGbh7/dsgQ5HXlek56+c0NiphqoUonJItx4YCFntnoCI2BL RFzw== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=JnI85gU6YQeNUNPXgYWoWQofjPEjOaI6yGnRM+D46Hs=; b=au3ZvkXvhPRA436Yz0tk9xZQThZlW/lQngprpaIn+4bedwxHe8jeZ4hGY36SL5YdD2 pXvJrlYp/BX36k6DejJQlmVuRlVDbMh2PA7Xz2C/OMxGo1QeUO2EAH6F5YmhEi2loBx6 Lf6VYC7ogP8f3CcMEeWO+/whvQEClh6b0TuDwF/LKoMJC8N7msBAsbyk5j5JAXruzn15 bpJgWfOpDceGZdlIVdl9uQ5NKjZQyLfP3V52VwEwY558wBnk25pkVs5Ro1NtvfFSGfrR IzebahJIV779Ih0CzmSc8x/1dd3XXdd3/VY6vRhy/tQfFibyfSle8GiJyCVCE6uFdiIl tlZA== X-Gm-Message-State: ALyK8tLd+zKohXTByboYRNL9qU2ZTUSr+vEc/mowlUI1SiBcEctVqdOuyXQce4ZYuHFVMQ== X-Received: by 10.66.47.196 with SMTP id f4mr15085101pan.126.1468427876935; Wed, 13 Jul 2016 09:37:56 -0700 (PDT) From: Bart Schaefer Message-Id: <160713093819.ZM21122@torch.brasslantern.com> Date: Wed, 13 Jul 2016 09:38:19 -0700 In-Reply-To: <53283.1468404826@hydra.kiddle.eu> Comments: In reply to Oliver Kiddle "Re: State of the ZLE region across new prompts" (Jul 13, 12:13pm) References: <160711212814.ZM15416@torch.brasslantern.com> <53283.1468404826@hydra.kiddle.eu> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: zsh-workers@zsh.org Subject: Re: State of the ZLE region across new prompts MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Seq: zsh-workers 38847 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? But I guess it would be useful if zle-line-finish sees the final state of the region. } How about the following rewording? I don't think it is the right place } in the documentation to enumerate all the ways in which the region can } be activated and deactivated Seems fine to me.