From: rif <rif@MIT.EDU> - 2002-10-12 05:22:09
|
Summary: I had several confusions with typeout windows and output. I think I understand now. If everything I give in this summary is correct, I am willing to write a patch to the "Typeout windows" info node, as well as some variable docstrings. Please confirm or correct these hypotheses: 1. lisp-no-popper affects exactly two functions in the ilisp distribution --- ilisp-display-output-default and ilisp-arglist-message-lisp. The Info Node "Typeout Windows" is misleading on this point --- it mentions that ilisp-display-output-default obeys the lisp-no-popper variable, but doesn't mention whether any other functions do or don't. It also says "An alternative to typeout windows is to always have the inferior Lisp buffer visible and have all output go there. Setting lisp-no-popper to t will cause all output to go to the inferior Lisp buffer." This should be clarified in various ways. The lisp-no-popper and ilisp-display-output-default docstrings are in direct contradiction on the subject of where outputs longer than one line are sent if lisp-no-popper is neither nil nor t. The lisp-no-popper docstring correctly states these go to a pop-up window (this is correct assuming ilisp-display-output-default is being used, lisp-no-popper needs to mention this), and the ilisp-display-output-default docstring incorrectly states it goes to the ilisp buffer (ie., the lisp listener). 2. ilisp-*use-frame-for-arglist-output-p* is very poorly named. This variable really refers to whether the arglist info goes somewhere *different* than the output from the inferior lisp --- in and of itself it has nothing to do with frames. In particular, all four combinations of this variable being t/nil and arglist info appearing in a frame or not are possible. The interaction between arglists and list-no-popper should also be mentioned. Basically, if list-no-popper is t, the arglist info will ALWAYS be shown via message. If list-no-popper is nil, then the output is passed to lisp-display-output, and it is only in this case that the values of ilisp-*use-frame-for-arglist-output-p* and ilisp-*use-frame-for-output* become relevant. End of summary. If everything I said above is correct, then I have a reasonable understanding of what's going on, and I can submit some documentation patches. Cheers, rif |