From: <ma...@at...> - 2000-11-09 23:12:03
|
Sam Steingold wrote: > > I believe I fixed the problem. > please try CLOCC/CLLIB/inspect.lisp with the current CVS clisp on Linux. Ok. I've tested this. Thanks for integrating part of my patches - this seems to have solved the browsing problem. Well done! Nevertheless there does remain one problem. And that seems to be related to #'lisp:run-program: I have one question: Is #'lisp:run-program supposed to return, after it was called and the program has been started sucessfully, or not? I have the following behavior: If I run #'inspect-cllib as follows (cllib::inspect-cllib '(1 2 3) :frontend :http :browser :netscape-remote) all works fine. Otherwise, if I do a (cllib::inspect-cllib '(1 2 3) :frontend :http :browser :lynx) or (cllib::inspect-cllib '(1 2 3) :frontend :http :browser :netscape) this will have no effect, e.g. no inspection is shown, because the browser is waiting for data, and this data is just not coming in. And this seems to be related to #'run-program. #'run-prog in shell.lisp calls run-program. If I start netscape manually by (lisp:run-program "netscape" :arguments '("")) this does not return after netscape was started. Same is true for lynx. It does only return, after a) I shut down Netscape b) I do C-c (Netscape is closed anyway) Do you have any ideas? I didn't notice this behavior before, because CLISP's #'browse-url starts netscape with the "remove" and "new-window" option. This is the case, when it works correctly. Cheers, Martin -- Homepage: http://www.atzmueller.net/ Email: ma...@at... |