From: Peter Stephenson <p.stephenson@samsung.com>
To: Zsh Users <zsh-users@zsh.org>
Subject: Re: Can periodic hook stop rescheduling?
Date: Tue, 13 Sep 2016 14:20:03 +0100 [thread overview]
Message-ID: <20160913142003.480cfd9c@pwslap01u.europe.root.pri> (raw)
In-Reply-To: <CAKc7PVDkrKD_2VyvO_2JigwfvU1m=3QwO4Vac=HgHZNbOOU7pA@mail.gmail.com>
On Tue, 13 Sep 2016 10:49:35 +0200
Sebastian Gniazdowski <sgniazdowski@gmail.com> wrote:
> I'm using sched to call a function. The problem is, it sometimes
> doesn't reschedule. sched +2 is the first line of the scheduled
> function, however I observed, that when running a completion and
> pressing Ctrl-C to abort something in it (when using
> :completion:*:*:*:default' menu yes select search) this Ctrl-C might
> somehow apparently reach scheduled function and block reschedule. I've
> added a protection via preexec hook – I check when scheduled function
> did last run and reschedule when a delay is detected.
The function that's being called is certainly not immune from getting
^C, and that can certainly stop "sched +2" in its tracks just like any
other command. The only general fix for this would be blocking SIGINT
sufficiently early that ^C doesn't hit this and restoring it later ---
but given sched +2 is the first line of the script anyway that doesn't
look promising.
You might have better results with
{
...
} always {
sched +2 ...
}
but it's still subject to the same problem if the ^C happens at the
wrong point.
This may need some lateral thinking.
pws
next prev parent reply other threads:[~2016-09-13 13:20 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20160913085130eucas1p19723ac09c11d596542360173e4a4b308@eucas1p1.samsung.com>
2016-09-13 8:49 ` Sebastian Gniazdowski
2016-09-13 13:20 ` Peter Stephenson [this message]
2016-09-13 13:34 ` 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=20160913142003.480cfd9c@pwslap01u.europe.root.pri \
--to=p.stephenson@samsung.com \
--cc=zsh-users@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).