* Any ideas for syntax of a task specification?
@ 2018-05-09 20:05 Sebastian Gniazdowski
0 siblings, 0 replies; only message in thread
From: Sebastian Gniazdowski @ 2018-05-09 20:05 UTC (permalink / raw)
To: Zsh hackers list
[-- Attachment #1: Type: text/plain, Size: 952 bytes --]
Hello,
I currently use following syntax of a task (the task is: file to source):
... atinit"code to be run before running task" \
atload"code to be run after running task" \
load"condition to load task, e.g. [[ $PROMPT = yes ]]" \
unload"condition to unload task, e.g. [[ $PROMPT = no ]]"
wait"time to wait before loading task, # of seconds, alternative to
'load'"
Background & motivation is: 1-code-line with substitution is sufficient to
detect task that needs to be run. The substitution uses code execution,
calls math function.
It's task-management, elastic scheduler, in few lines of code, fast.
So I wonder: has anyone seen in e.g. daily job, in some other technology, a
syntax to specify complex things, tasks, that could be used? Or has some
idea? Zsh can serialize hashes, so ZSH_TASKS array (on which the
1-code-line substitution operates) can hold very rich task specification.
--
Best regards,
Sebastian Gniazdowski
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2018-05-09 20:05 UTC | newest]
Thread overview: (only message) (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2018-05-09 20:05 Any ideas for syntax of a task specification? Sebastian Gniazdowski
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).