Age | Commit message (Collapse) | Author |
|
|
|
Thanks to Joerg Wittenberger for the suggestion to add proc:pid and
signal-process.
|
|
|
|
|
|
|
|
|
|
This is what scsh does as well, and is more like a regular UNIX shell.
Thanks to Haochi Kiang for reporting the bug and providing a patch.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
see some problems occurring
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
process-wait, which could lead to trouble in user code when compiled with scrutiny and/or specialization. This procedure returns the values in a different order for ease of use. May be a bit confusing...
|
|
for scsh-process to fix bogus optimization of 'signal-handler' due to invalid scrutiny type
|
|
|
|
|
|
|
|
segfaults immediately. TODO: Figure out why
|
|
|
|
|
|
|
|
factors that determine process interleaving, ensuring it gets processed through the pipeline rather than on the same descriptor by mangling it through 'tr'. Fix <<-redirection by reopening output port on new descriptor and explicitly setting up the input port to the given fd in the parent process
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
garbage for run/sexp's test
|
|
ensure processes don't hang when they keep writing while the pipe buffer is full. Instead, it would kill the process with sigpipe
|