-
Notifications
You must be signed in to change notification settings - Fork 19
Description
(This message has been a journey.)
After more research, I cannot find a specific "signal" mechanism so that the R expression can immediately be signaled back to the main host while the rest of the expression continues to execute.
Long-story-short, I enabled
daemons(..., output=TRUE)to see errors/warnings immediately, nice that they are passed immediately. I thought they may be passed back to the local process as"condition"s in which case handlers would be able to work on them, but alas I believe they are being merelycat'ed (or equivalent) to the local console.From this, two questions:
- Is it possible to tag the remote-output with a particular
"condition"where its default local handler is merelycat(cond)? This would continue the current behavior, but would allow a calling handler to deal with remote output distinctly from local output. (If always doing this as a condition is concerning, it could be as an option, something likedaemons(.., output=T, output_condition=T).)- I see the since-removed
.signal=argument which referencesnanonext::cv(), iscv()applicable here? Is there a way to allow remote signals (distinct from console output) to be caught via the normal R mechanisms?I'm adding this comment mostly to say that I continue to look into the source to hope to self-answer, but I'm not finding something to lead me to a working solution. Since this discussion has spiraled from
unassigned()to a bit more, would it be better as a Discussion?