From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (qmail 26940 invoked by alias); 15 Sep 2016 22:19:35 -0000 Mailing-List: contact zsh-workers-help@zsh.org; run by ezmlm Precedence: bulk X-No-Archive: yes List-Id: Zsh Workers List List-Post: List-Help: X-Seq: 39352 Received: (qmail 24202 invoked from network); 15 Sep 2016 22:19:35 -0000 X-Qmail-Scanner-Diagnostics: from mail-pf0-f171.google.com by f.primenet.com.au (envelope-from , uid 7791) with qmail-scanner-2.11 (clamdscan: 0.99.2/21882. spamassassin: 3.4.1. Clear:RC:0(209.85.192.171):SA:0(0.0/5.0):. Processed in 0.76561 secs); 15 Sep 2016 22:19:35 -0000 X-Spam-Checker-Version: SpamAssassin 3.4.1 (2015-04-28) on f.primenet.com.au X-Spam-Level: X-Spam-Status: No, score=0.0 required=5.0 tests=T_DKIM_INVALID autolearn=unavailable autolearn_force=no version=3.4.1 X-Envelope-From: schaefer@brasslantern.com X-Qmail-Scanner-Mime-Attachments: | X-Qmail-Scanner-Zip-Files: | Received-SPF: none (ns1.primenet.com.au: domain at brasslantern.com does not designate permitted sender hosts) 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=C1hPof6j9cfkCrUBdGEuoAuObXe3Od4kQ6p1osCWFDA=; b=tPkvtHp94d8eM9LaL8EEcDKWdTOeDQ5NL+dYS1pRECTriTZCPUUur03acZ7oqG8YFw y/RF90TkRIwGbjTvZ/B8lUR1SCM03BBb3gXwVkaL4LLrzB00C9PMsZAdUQPhUQDqytTr HruBcuaDuZ7sQGVQVjqmPf3Q0y0mTQ+8js05f2oy7rkfEoeKiN+ZqQsC7f1UoJQ1FSHv /OPhmvkRkzHn0UYW3AwyKtk6h+zJcamBdLT2kHPahUL3HVzbvpNXx0PgcbbT6iFCoiR3 zLXjy9J6fnd72o0tDQOF29HL1TQZhCz1lTAoYL7I/YuEjloie+5ORE+jfjmyO1fNIG1F ZiEQ== X-Google-DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=1e100.net; s=20130820; h=x-gm-message-state:from:message-id:date:in-reply-to:comments :references:to:subject:mime-version; bh=C1hPof6j9cfkCrUBdGEuoAuObXe3Od4kQ6p1osCWFDA=; b=cYp2wB8rBuFu8jv26U47w4Dv9jpgMnUWaupsWd9lK84JkKtpoRLAp0iLb2p36tNx/M FfoG7IFKtdyWkS/JXYP9JrRBLnUVrgFPDqxSaamKBRMO0s0XmR0ek8sG79Ix+jOH7pK2 XQmm9h5i65V6qHgBEXfUgjWYNWFoQJjX3YFrTJRkhBCLjY25Pfs6ThlebmEfOu7fOaUC 2e1gqcwivJHMsXfDgPhX7dLD04XDxSCE+WvXLFMZxzq0gh/cap9F1Zu5wqDGNUXOPHrh LuGGGPJXGqKv1PFsh4n1ajTW3y2RdJhZ8M8Bq+7UqB9ISYPGKHioleGbKcQw9cyb/y36 K9Jw== X-Gm-Message-State: AE9vXwO0tL7MJsK1/LhfhnzCu4tpXxwJt1k57Nfo5Nx9t5/cod6OzDuoGDmZA8sGGbF7LQ== X-Received: by 10.98.93.204 with SMTP id n73mr18106980pfj.87.1473977968702; Thu, 15 Sep 2016 15:19:28 -0700 (PDT) From: Bart Schaefer Message-Id: <160915151942.ZM3385@torch.brasslantern.com> Date: Thu, 15 Sep 2016 15:19:42 -0700 In-Reply-To: Comments: In reply to Sebastian Gniazdowski "Re: Can periodic hook stop rescheduling?" (Sep 15, 12:18pm) References: <20160913142003.480cfd9c@pwslap01u.europe.root.pri> <160913091822.ZM29020@torch.brasslantern.com> <20160914200421.021c559e@ntlworld.com> <160914215152.ZM519@torch.brasslantern.com> X-Mailer: OpenZMail Classic (0.9.2 24April2005) To: Zsh hackers list Subject: Re: Can periodic hook stop rescheduling? MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii 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.