Zsh Mailing List Archive
Messages sorted by:
Re: Where to start debugging zle recursive-edit? / Ctrl-C
- X-seq: zsh-workers 39430
- From: Sebastian Gniazdowski <sgniazdowski@xxxxxxxxx>
- To: Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx>
- Subject: Re: Where to start debugging zle recursive-edit? / Ctrl-C
- Date: Sat, 24 Sep 2016 22:58:19 +0200
- Cc: Zsh hackers list <zsh-workers@xxxxxxx>
- Dkim-signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=gmail.com; s=20120113; h=mime-version:in-reply-to:references:from:date:message-id:subject:to :cc; bh=mtQq6HvPj2y8xHPWUcCn1myt4jMAOr3YSKyS0b8m+Ik=; b=whtXNZpjce3C9b7aNsrR7kyoxlyQ2fRptEPOs6oA8KnCS3bIv56I6+ObaBCwAofUPh L5//EZOu3wTAc4hQFD+uqzRN4mstODi+EBy8Qh8JJEi69Go6g8d6pJ738L1Vdwfa8t0G xp4RuHEetOzU/ItuGewHqreCVkJlzWHLHCUJSGVjM+36ZWUlKLjV3GEZJlp2mAufSL9M Azt4S0NP2fuiqn2ugetb5auxRle92GPzCJHLC6Dm7VtLEpbufViJGVFXFmYE1YJWLg1i 4rnXhQC/daYr7a3qPA20cjHTRZl07RDexby3iAJFAqIapk/qF3wzzISJ+CoE+CjSZQ9L wHnA==
- In-reply-to: <160924133140.ZM29034@torch.brasslantern.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> <160924133140.ZM29034@torch.brasslantern.com>
On 24 September 2016 at 22:31, Bart Schaefer <schaefer@xxxxxxxxxxxxxxxx> wrote:
> 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.
That would explain what at first glance looks surprising.
> Does emacs mode vs. viins or vicmd matter? Does (un)setopt multibyte?
I create custom keymap from emac's:
Rather hard to test viins and vicmd? Might try with multibyte when I
spot this happening and repeating. And one session now had this. Doing
unsetopt multibyte stopped this, restoring the option didn't cause the
issue to come back.
> } 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.
It's 5.1.1, and I've tested rather identical setup in coincidence:
Proposed a possible fix but user didn't respond if it helped:
- bindkey -N zhcw main
+ bindkey -N zhcw emacs
> } 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).
Thanks, will sure get on that tomorrow. I also sometimes get crashes.
Terminal window closes. Any tips for generating coredumps on OS X? I'm
able to google that when will have time, but also wanted to disable
-O, and ./configure --help | grep -i opt didn't show any option.
Messages sorted by: