From mboxrd@z Thu Jan  1 00:00:00 1970
Return-Path: <zsh-workers-return-39428-mason-zsh=primenet.com.au@zsh.org>
Received: (qmail 27379 invoked by alias); 24 Sep 2016 17:30:00 -0000
Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm
Precedence: bulk
X-No-Archive: yes
List-Id: Zsh Workers List <zsh-workers.zsh.org>
List-Post: <mailto:zsh-workers@zsh.org>
List-Help: <mailto:zsh-workers-help@zsh.org>
X-Seq: 39428
Received: (qmail 28646 invoked from network); 24 Sep 2016 17:30:00 -0000
X-Qmail-Scanner-Diagnostics: from mail-qk0-f174.google.com by f.primenet.com.au (envelope-from <sgniazdowski@gmail.com>, uid 7791) with qmail-scanner-2.11 
 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1.  
 Clear:RC:0(209.85.220.174):SA:0(0.5/5.0):. 
 Processed in 0.446208 secs); 24 Sep 2016 17:30: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.5 required=5.0 tests=DATE_IN_PAST_24_48,
	FREEMAIL_FROM,SPF_PASS,T_DKIM_INVALID autolearn=no autolearn_force=no
	version=3.4.1
X-Envelope-From: sgniazdowski@gmail.com
X-Qmail-Scanner-Mime-Attachments: |
X-Qmail-Scanner-Zip-Files: |
Received-SPF: pass (ns1.primenet.com.au: SPF record at _netblocks.google.com designates 209.85.220.174 as permitted sender)
DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=gmail.com; s=20120113;
        h=mime-version:from:date:message-id:subject:to;
        bh=VZ4GzoUjunhd+R47DnX7ovly0S61AWGml2HRg+oJ2T8=;
        b=bJpTnfImYH9ZeLmaD67F747z3ECI4yW5p59qOo2vYA5ZUuFx3wNSm3Qy6qtpo4GxWl
         kn3nM2d/12p0ao4Gp56H6WcOLx6OebXI0PKRRQiZGXE4BicdBHehLLU7z8fNIb3bfc+D
         NLH3MY/4hJ/iZcGEJ9zQDH5VtKqKJS1STkKVvpV8VW34eyFQ38EaYgdxErYo60hNnkVa
         WeKMDAKa7J/siXAaYX48LXIeykz0rMSeEBOpbTcFKG3VGQq3Sog7EZcXMN/TKJvxXhth
         HGnVcR9kkd/MCMEfqLCDB0cEVX61CR8K84ye+hnrdTR4BFGBNehVuHywL8ocXEgehsKm
         2xrA==
X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed;
        d=1e100.net; s=20130820;
        h=x-gm-message-state:mime-version:from:date:message-id:subject:to;
        bh=VZ4GzoUjunhd+R47DnX7ovly0S61AWGml2HRg+oJ2T8=;
        b=L556b1F9yJ2OjAv8Yoq+EmemUpl44bL+3Gqd4FXZrFxeeNJkJBw7sBO9nRWeXoLSYC
         lW8HyfYpG3tmDghEMxU4rkYKhAphESZWEKEQEihhDfdZEouUOJmzQkubQ9EGU3NAS406
         EppCBF0QjHsetiF/ybOo0PKF/B/7RE2HbCrBiW0odPDqpk+49c7unbIXT/R1e6IGc6qz
         XpkhmWp4x4KGolkqZMgKAIi/PXyv+/Y3funQSYRannVj7tWxQZupcnnzQwNwR8f1pvpj
         hovqizMpy6muJxtwnNB1LCFhk/emBjbanN+BocWnUQgjFLvxCS06bxjAoWEP6dd0sDSB
         eb7A==
X-Gm-Message-State: AA6/9Rnn0YzUo2yQgp5XH1ReBs4JqinhVXXy9fWTsixKETzza1AoUbKueBzP2Ja+TCvC11AD+HIk8Q4vnvhVpg==
X-Received: by 10.55.19.105 with SMTP id d102mr8398826qkh.190.1474648009146;
 Fri, 23 Sep 2016 09:26:49 -0700 (PDT)
MIME-Version: 1.0
From: Sebastian Gniazdowski <sgniazdowski@gmail.com>
Date: Fri, 23 Sep 2016 18:26:28 +0200
Message-ID: <CAKc7PVBvm+u5QQQZo+6QEQw4bRHx1br5K-A6y_6pAuP8+KCbcQ@mail.gmail.com>
Subject: Where to start debugging zle recursive-edit? / Ctrl-C
To: Zsh hackers list <zsh-workers@zsh.org>
Content-Type: text/plain; charset=UTF-8

Hello,
I use a POSTDISPLAY interface for Ctrl-R, that works inside
.zle-recursive edit. Occurring problems with Ctrl-C every day. Some
limited response, not instant cancel of search, once even full
blockade of interruption. Funny that it became much more intensive
after adding few custom keymap's bindings for left/right cursors, page
up/page down keys. Also one user reports that Ctrl-C crashes Zsh.
Would add a debug print somewhere and observe, then extend the
debugging. But where?

Best regards,
Sebastian Gniazdowski