Re: Using ACL with ILISP on MS Windows

Marco Antoniotti <[email protected]> writes:

> > > P.S.: Your approach of scanning the whole buffer with every output is
> > > hardly satisfactory.  Maybe you could merge those parts with
> > > strip-ctrl-m from GNU Emacs comint-mode into the ilisp version?
> > 
> > I realize that this approach is sub-optimal ;-) however, I am just 
> > trying to find something that works first and will optimize it 
> > later. I would like to find the best place to insert the scrubbing code
> > (I've tried the RET key processing and the lisp output display functions
> > in ILISP so far). 
> > 
> > Any ideas on where in ILISP would be the best place to do the scrub
> > would be appreciated.
> > 
> > Thanks for your suggestions to date Nicolas.
> > 
> 
> Yep.  ILISP uses the code in file `comint-ipc' which dates back to
> 1990.  The file was necessary to extend the then deficient standard
> `comint'.
> 
> Of course, an update to more modern `comint' for the latest (X)Emacs
> would be s good thing.
> 
> Any taker?  :)
> 
> Cheers

Not me, because it would take me much too long.  Also, ilisp and
comint appear to be linked quite intricately.  But hopefully, some
expert will see it differently:-)

[I have looked a bit on the code as it is, but can't make too much out
of it.  ilisp-display-output-in-lisp-listener seems to call
comint-insert directly, which I find somewhat astonishing because no
filter is applied then.  Anyway, whitespace is filtered out here, so
maybe Bill could modify something at this place (hope it's the
relevant one):

(defun ilisp-display-output-in-lisp-listener (output ilisp-output-sink)
  "Display output in the ilisp buffer"
  ...
  (comint-insert 
     (concat 
      (if ilisp-last-message
	  (concat ";;; " ilisp-last-message "\n"))
      (comint-remove-whitespace output)
      "\n"
      ilisp-last-prompt))
)
]

Bye, Nicolas.