[16:39] <wraiden> Hello :)
[18:56] <wraiden> *reading job_emit_event*
[19:00] <Keybuk> wraiden: good luck
[19:00] <Keybuk> the last person who went in there never came out
[19:20] <wraiden> hehe
[19:20] <wraiden> i think i have found the point to add the alias handling
[19:21] <Keybuk> it would be in there, yes
[19:21] <wraiden> i think i move the environment construction into an helper as i have to construkt the environment for the job event itself and all aliases that might be set...
[19:22] <wraiden> or is it possibe to overwrite the JOB in an already constructed environment ?
[19:22] <wraiden> that would make it very easy *G*
[19:23] <Keybuk> yeah, you can keep setting JOB to overwrite it
[19:23] <Keybuk> see environ.c
[19:23] <wraiden> and it will hold its position as the first env var on the event?
[19:24] <Keybuk> yes
[19:25] <Keybuk> see environ_add()
[19:25] <Keybuk> (provided you go through that function, of course)
[19:26] <Keybuk> environ_set() calls environ_add() fwiw
[19:26] <wraiden> nice and handy *g*
[19:38] <wraiden> where does the code actualy block until all jobs that hook into a blocking event are processed?
[19:42] <Keybuk> the code doesn't block per-se
[19:43] <Keybuk> job_change_state sets job->blocker to the return value of job_emit_event
[19:43] <Keybuk> and doesn't change state to the next one, so ends
[19:44] <Keybuk> event_finished() is what, when an event reaches zero blockers, calls job_change_state to unblock the job
[19:45] <wraiden> if i implement the aliases as multiple independent blocking events...
[19:45] <wraiden> then i have to check if no other alias event is still blocking
[19:45] <wraiden> mhm
[19:52] <Keybuk> interesting
[19:52] <Keybuk> yeah you may have to extend things
[20:01] <wraiden> if i understand the code right than i can add multiple blocking events to the main jobs event->blocking