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.


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