I'have used ILISP (with Xemacs and CMUCL) quite a while now but still
I'm not very familiar with its features and capabilities.
I have two questions concerning the buffers and their interaction:
1. Without (setf lisp-no-popper t) Xemacs hangs after some evaluations
and/or compilations. Is this a configuration problem?
2. When I define the function
(defun test ()
(loop for i from 0 to 99 do
(loop for j from 0 below 3000 do (* j i)) do
(print i) (force-output *standard-output*)))
within a lisp-source buffer, evaluate it and then evaluate (test) within
this buffer the output is written to the *cmulisp* buffer only after the
function has finished. When typing (test) <Return> in the *cmulisp*
buffer, the output is written immediatly. Is there any way to make ILISP
write the output immediatly
when issuing the eval command within the lisp-source buffer? The problem
is that in case of large amounts of output Xemacs hangs (probably
because Xemacs blocks itself due to a full output buffer).
I would be very appreciative for help
With kind regards
From: Nicolas Neuss <Nicolas.N<euss@iw...> - 2003-05-23 13:43:00
Rolf Wester <wester@...> writes:
> 2. When I define the function
> (defun test ()
> (loop for i from 0 to 99 do
> (loop for j from 0 below 3000 do (* j i)) do
> (print i) (force-output *standard-output*)))
I had the same problem and do not quite understand the solution you give on
c.l.l. involving ilisp-*use-fsf-compliant-keybindings*. Do you mean to use
the "-and-go" versions of evaluation and compilation functions? This
works, but what if I want to remain in my sourc code window? In this case,
the setting of the fsf-keybindings does not matter for me.
I have an ugly solution which is to define a keyboard macro consisting of
(eval-and-go & jumping back). If nobody posts a better solution I'll
probably turn this into a function and set it to some key.