zsh-workers
 help / color / mirror / code / Atom feed
From: Bart Schaefer <schaefer@brasslantern.com>
To: Zsh hackers list <zsh-workers@zsh.org>
Subject: Re: Can periodic hook stop rescheduling?
Date: Thu, 15 Sep 2016 15:19:42 -0700	[thread overview]
Message-ID: <160915151942.ZM3385@torch.brasslantern.com> (raw)
In-Reply-To: <CAKc7PVBPLZ6kG6=w62aTWG3XjfXQi7TEmgunTZ0Ch4a=db8Ubg@mail.gmail.com>

On Sep 15, 12:18pm, Sebastian Gniazdowski wrote:
} 
} This might be a general topic of descheduling, its not-full
} convenience. It is done via: sched -item (number of item on sched's
} list as man page says). Apparently one has to fork, parse `sched`
} output, establish item nr and invoke sched -item.

Well, sched was intended as a purely interactive feature since it
only works at all in interactive shells, so the assumption at the
time was that a human would read the sched output and remove the
corresponding item.  Hiding the scheduled tasks behind some kind
of UI and manipulating them programatically was not in the plan.

At the moment it's like you're complaining that it's inconvenient
that your 1989 Volvo doesn't have keyless ignition.

} new builtin is rather a unpleasant thing, one has to fill some
} registration tables probably? What are chances for schedid, ksched,
} automatic rescheduling? Maybe I could implement them

They're more likely to show up as options to "sched" itself than as
new separate builtins.

} PS2. About my question on periodic hook, is it immune to Ctrl-C?

It's not immune in the sense that you can interrupt the function
while it's running, but it is immune in that it keeps repeating as
long as PERIOD has a value even if it was interrupted last time.


      reply	other threads:[~2016-09-15 22:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CGME20160913085130eucas1p19723ac09c11d596542360173e4a4b308@eucas1p1.samsung.com>
     [not found] ` <CAKc7PVDkrKD_2VyvO_2JigwfvU1m=3QwO4Vac=HgHZNbOOU7pA@mail.gmail.com>
     [not found]   ` <20160913142003.480cfd9c@pwslap01u.europe.root.pri>
2016-09-13 16:18     ` Bart Schaefer
2016-09-14 19:04       ` Peter Stephenson
2016-09-15  4:51         ` Bart Schaefer
2016-09-15 10:18           ` Sebastian Gniazdowski
2016-09-15 22:19             ` Bart Schaefer [this message]

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=160915151942.ZM3385@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).