Re: C-c C-c / C-c c

Hannu Koivisto <[email protected]> writes:

> > Nicolas Neuss <[email protected]> writes:
> > 
> > > 1. When the Lisp buffer is not visible the command eval-next-sexp does not
> > >    work (eval-next-sexp-and-go-lisp does) I get the error
> > >
> > > error in process filter: lisp-pop-to-buffer: No buffer named  *Output*
> > > error in process filter: No buffer named  *Output*
> 
> > I have noticed this as well, it is clearly a bug.
> 
> I have now simply put
> 
> (setf (ilisp-output-sink-buffer ilisp-output) "*cmulisp*")
> 
> into my ilisp-load-hook.  But a good patch for ilisp-out.el is not clear to
> me...
> 
> > > 2. Strangely, the meaning for the keys for C-c C-c and C-c c (and also C-c
> > >    C-n and C-c n, etc.) are exchanged on both machines[1].  I wonder how
> > 
> > This does not make sense.  As far as I can see, C-c c and C-c n
> > should not be bound to anything whether you use FSF keybindings or
> > not.  With FSF bindings, C-c C-c should be compile-defun-lisp.
> 
> I have now set
> 
> (setq ilisp-*use-fsf-compliant-keybindings* t)
> 
> I guess this is what was missing on one of my machines and was set by the
> site-wide initialization file on the other.
> 
> Thanks for the response,
> 
> Nicolas.

I am new to this list, I was forwarded this message by a coworker who
recognized a gripe I had yesterday and passed it along to me.  If I'm
off topic I apologize.

I've been using the ilisp debian package from the testing distro for a
while now and have had a similar problem in xemacs 21.4. When compiling
or evaling I would routinely get the error "Selecting deleted or
non-existent buffer" in my mini-buffer.  If I had the inferior lisp
buffer open the problem did not manifest.  Being perhaps not as intrepid
as I should be I put up with it until yesterday at whihc point I set out
to find a temporary solution to tide me over (I guess I'm pretty lazy at
heart).

The kludge I found was to comment out the following three lines in
ilisp-bury-output-internal in ilisp-out.el v 1.13 

;(with-current-buffer buffer
;  (erase-buffer))
;(bury-buffer buffer)

The net effect for me is that the error message has gone away and every
time I compile or eval a defun the inferior lisp buffer pops up again.
I have yet to take the time to read the ilisp source, though I have
tentatively scheduled my first real foray for this evening. I'll follow
up with anything that I discover.

-- 
Lee Ayres <[email protected]>


-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf