Zsh Mailing List Archive
Messages sorted by:
Re: Where to start debugging zle recursive-edit? / Ctrl-C
- X-seq: zsh-workers 39429
- From: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- To: Zsh hackers list <zsh-workers@xxxxxxx>
- Subject: Re: Where to start debugging zle recursive-edit? / Ctrl-C
- Date: Sat, 24 Sep 2016 13:31:40 -0700
- 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==
- In-reply-to: <CAKc7PVBvm+u5QQQZo+6QEQw4bRHx1br5K-A6y_6pAuP8+KCbcQ@mail.gmail.com>
- List-help: <mailto:firstname.lastname@example.org>
- List-id: Zsh Workers List <zsh-workers.zsh.org>
- List-post: <mailto:email@example.com>
- Mailing-list: contact zsh-workers-help@xxxxxxx; run by ezmlm
- References: <CAKc7PVBvm+u5QQQZo+6QEQw4bRHx1br5K-A6y_6pAuP8+KCbcQ@mail.gmail.com>
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).
Messages sorted by: