This problem is with runhugs not Hugs, right?

Makes no difference, really. For instance, I sometimes "script" Hugs by piping commands and input into it (very useful to get all that browsing/info support from within your favorite editor, without having to extend/dll-convert/re-distribute hugs server;-):

$ cat > /tmp/foo.hs main = getLine >>= print

$ echo "main" | hugs /tmp/foo.hs $ echo ":browse" | hugs /tmp/foo.hs $ echo 'print "hello world!"' | hugs Which reminds me: would it be difficult to separate hugs into a dll and an executable which just calls (renamed) main in the dll? Vim permits calling functions in dlls. Or is there any portable way to send Hugs into the background and have access to its stdin and stdout (the obvious named pipes won't work in windows, afaik)? Claus