From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 29692 invoked by alias); 7 Nov 2014 00:37:47 -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: 33625 Received: (qmail 14497 invoked from network); 7 Nov 2014 00:37:46 -0000 X-Spam-Checker-Version: SpamAssassin 3.3.2 (2011-06-06) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=-2.6 required=5.0 tests=BAYES_00,HTML_MESSAGE, RCVD_IN_DNSWL_LOW autolearn=ham version=3.3.2 X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:mime-version:in-reply-to:references:date :message-id:subject:from:to:content-type; bh=oUh+F4KZjNU4I7strqWrFNDttjZ9wazAYffbC79Nz80=; b=jRZhhvvKbOHYSqAgqBabfSHXsZT/wRDId8MjxHANNu/5nsWfrET3FJ4OzGv7w4fXwL ePH0r39KoQ+LyPtaAkJ0bfOLj4qm8PwniZtS1Hz0xdcdWJbMt2YzX8BgEXb2oaqtXp/m NjdAmR2qH7Uw7AVPQQZmjM5wesES+V/Ttn4lD7d72NsYBGf09UCyqr7vVeo0t96STVTW J0i8fJ2WhCO6o09Rf5ChHgylOmXNxM2vFLFvWUOxsk2TA3ayrXGmzZ/LvI7OGQ+3eO5L 4UNiQR3VlhYZmKUtI9t1W2VdtEqAl2bqDyGLaDH8j8Y0nBUCmR6+LjIkBNsC9J+O/Upd YqmA== X-Gm-Message-State: ALoCoQmjQugqel4730VsZUEMYp3NdNevcv8qgtSPN8lMPdOgGYlFQej1E5RqsVAyR9ymePFDch0W MIME-Version: 1.0 X-Received: by 10.140.87.11 with SMTP id q11mr5948112qgd.6.1415320661285; Thu, 06 Nov 2014 16:37:41 -0800 (PST) In-Reply-To: <8414.1415317703@thecus.kiddle.eu> References: <8414.1415317703@thecus.kiddle.eu> Date: Thu, 6 Nov 2014 16:37:41 -0800 Message-ID: Subject: Re: PATCH: keep region active when widget fails From: Bart Schaefer To: Zsh hackers list Content-Type: multipart/alternative; boundary=001a113a61de42737205073a054b --001a113a61de42737205073a054b Content-Type: text/plain; charset=UTF-8 On Nov 6, 2014 3:55 PM, "Oliver Kiddle" wrote: > > Does anyone know why we set region_active to false in handlefeep()? It's probably so that an explicit call to "zle beep" from a user-defined widget will end the region as a side-effect ... PWS should be able to confirm because it has been that way since the initial zle highlighting patch. Zle could probably use a way to signal a non-fatal error, send-break is a bit excessive. --001a113a61de42737205073a054b--