| | I know that Hemlock maintenance is not a high priority for most of you (nor | should it be), but I ahve a question and I thought one of you might have a | quick answer before I dig in myself... | | I'm running CMUCL 18d on a variety of systems, mostly Red Hat Linux. I | like to use Hemlock as the front-end to the Lisp listener -- it's nice to | have my favorite editor between me and the interpreter. But a couple of my | programs ask for user input and then read from *standard-input*, and | Hemlock complains about this: "Can't read from thsi stream while hemlock is | running" or some such message. | | Is there an easy fix for this? |
There is a WITHOUT-HEMLOCK macro but I could never figure out exactly what it was for or when to use it. | For what it may be worth, the Emacs-like editor front-end in Lispworks | doesn't have this problem. It quite happily accepts user input via the | same editor window that normally sends input to the listener. | Not sure what problem you are having. (read *standard-input*) in the slave seems to the right thing here (right meaning I can then type stuff that gets read). Paul
