From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Where to start debugging zle recursive-edit? / Ctrl-C
Date: Fri, 30 Sep 2016 13:44:46 -0700 [thread overview]
Message-ID: <160930134446.ZM17118@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVCEbqF7KudsZDEadTM4988Ega3dFS7cEPCcYv=mNfntLg@mail.gmail.com>
On Sep 30, 3:30pm, Sebastian Gniazdowski wrote:
}
} So, the linked list doesn't have any elements, and calc_timeout()
} exits with ZTM_NONE instead of ZTM_FUNC
If I recall correctly how this is architected ...
This must mean that you are interrupting the scheduled function itself,
before it has a chance to execute "sched" and reset its timer.
Because you are in recursive-edit, interrupting does not go all they
way back to the top-level prompt where the precmd hook would restore
the timer, so it remains unscheduled until the current zle session
is done and precmd runs again.
You may need to find a more aggressive place to reset the timer, such
as in the zle-line-pre-redraw hook, or else create a wrapper widget
for recursive-edit.
Either way you'd want to examine $zle_scheduled_events to see if the
timer is still pending, before scheduling it again.
Or possibly you could switch from doing this with a timer scheduled
function to using a "zle -F" handler function.
next prev parent reply other threads:[~2016-09-30 20:51 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 16:26 Sebastian Gniazdowski
2016-09-24 20:31 ` Bart Schaefer
2016-09-24 20:58 ` Sebastian Gniazdowski
2016-09-25 7:09 ` Daniel Shahaf
2016-09-26 22:16 ` Sebastian Gniazdowski
2016-09-27 16:09 ` Bart Schaefer
2016-09-29 9:30 ` Sebastian Gniazdowski
2016-09-29 17:07 ` Bart Schaefer
2016-09-30 9:04 ` Sebastian Gniazdowski
2016-09-30 11:28 ` Sebastian Gniazdowski
2016-09-30 13:30 ` Sebastian Gniazdowski
2016-09-30 20:44 ` Bart Schaefer [this message]
2016-10-02 16:26 ` Sebastian Gniazdowski
2016-10-02 17:37 ` Sebastian Gniazdowski
2016-10-05 5:31 ` Sebastian Gniazdowski
2016-10-05 6:14 ` Bart Schaefer
2016-10-05 10:27 ` Sebastian Gniazdowski
2016-10-05 18:31 ` Bart Schaefer
2016-10-05 20:36 ` Sebastian Gniazdowski
2016-09-30 21:45 ` Bart Schaefer
2016-09-30 21:54 ` Sebastian Gniazdowski
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=160930134446.ZM17118@torch.brasslantern.com \
--to=schaefer@brasslantern.com \
--cc=zsh-workers@zsh.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.vuxu.org/mirror/zsh/
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).