From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 21102 invoked by alias); 24 Sep 2016 20:31: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: 39429 Received: (qmail 27376 invoked from network); 24 Sep 2016 20:31:38 -0000 X-Qmail-Scanner-Diagnostics: from mail-pf0-f173.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.192.173):SA:0(0.0/5.0):. Processed in 0.569196 secs); 24 Sep 2016 20:31: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=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=4gOxu66K40oJoNXNl87bLYmCkSF+b1n8t7WPsMLNI7g=; b=0zYa0xyo7td/zfzFS+tlP3j5Vamr/gWgfbcbbQwJmBAW2HOH5ibO0Xa1RDfiKmycFy fhh75waWC4qOijbyOgq39f57BFrkIv3dbVyyLmT33jsfVLx3ehIfRaV5pAritOu7d42w 6BBWmyNHaShzWxO2hH7anN5TNy45WnPfzB73p8QAmzgfkg4y/zNSjmV2Gkt26H/M7gow GVtHWaYK90w/80aDDzx7x2S4Ko8yuRr3G57MBNgpAkMSmiy7fmaPnxfvP8gQj7g7FS3g i85LJAosFZMUpYNNPo7DqpCd5RN1ojo1fx3om9XK4Es3UhTH9sMPBmlPdO8BXdUjgn2Q ARJg== 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=4gOxu66K40oJoNXNl87bLYmCkSF+b1n8t7WPsMLNI7g=; b=dgbDpZfUT5OTo0lbS5g57wwMqVbWpAJvyobg0mxI8FMUjR4Bf67cHhXMNazIq4B6O8 3CzzL3f0JNUoXbKDOnAEz+fMuPV4KMklcPtTSKvmSpHUkEtwclfV4hTqV1xCWgMHXg+A 9D6cBJp4xmoiqv4w6VXop2AAEhPp+Dt3o1O3U3FYeTeqcs+pk9IGmqWXn7ZoIatsk1z0 ju6Pr0rMrykrlB0UG8nsIL1EvB67dcVVWnpwWpZqFvPAKFXQmxgnSar76dXKAqE6aHJM ixCO9Dn536l9ptS5FFwpjhLMjWsZtakuPQDit/4uJliKs6uIRTWr+f4GREirwtkFhZWw 7umw== X-Gm-Message-State: AE9vXwM2pMA3mD2EJjQKhioWQGms4LGoKmZXr7HjctHCQKmP9w0CbRxRfxTk8x2+kgdSBA== X-Received: by 10.98.60.68 with SMTP id j65mr24288124pfa.55.1474749092915; Sat, 24 Sep 2016 13:31:32 -0700 (PDT) From: Bart Schaefer Message-Id: <160924133140.ZM29034@torch.brasslantern.com> Date: Sat, 24 Sep 2016 13:31:40 -0700 In-Reply-To: Comments: In reply to Sebastian Gniazdowski "Where to start debugging zle recursive-edit? / Ctrl-C" (Sep 23, 6:26pm) References: X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh hackers list Subject: Re: Where to start debugging zle recursive-edit? / Ctrl-C MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii On Sep 23, 6:26pm, Sebastian Gniazdowski wrote: } } I use a POSTDISPLAY interface for Ctrl-R, that works inside } .zle-recursive edit. Occurring problems with Ctrl-C every day. } [...] Funny that it became much more intensive after adding } few custom keymap's bindings for left/right cursors This probably means that the ^C is arriving while zle is waiting to see if a binding has multiple "keystrokes" before determining what widget to call. Does emacs mode vs. viins or vicmd matter? Does (un)setopt multibyte? } Also one user reports that Ctrl-C crashes Zsh. If this is with the latest build from git, it might be related to the recently-introduced signal-handling problem with functions that Daniel and I have been discussing elsewhere. } Would add a debug print somewhere and observe, then extend the } debugging. But where? You're probably interested in getbyte() in zle_main.c, but you might also attach with a debugger and put a breakpoint in zhandler so you can get a stack trace of where the handler is being called [if it is]. (Starting the debugger first and running zsh inside it won't work as well because the debugger itself will trap the signals).