Note that there are some explanatory texts on larger screens.

plurals
  1. POI can't close the last parenthesis and send my function to the REPL using lisp-mode in Slime
    text
    copied!<p>This is a very simple question. I have installed Emacs 22.2.1 (from the Ubuntu (9.04) repo and I downloaded Slime-current from the repo on their homepage.</p> <p>I followed the instructions provided with slime and it works. I can start slime and use it as expected.</p> <p>However, when I enter lisp-mode (M-x lisp-mode) I can no longer interact with the REPL. Nothing I type works, the cursor just moves to the next line when I press enter.</p> <p>Does anyone have a fix for this?</p> <p><strong>Edit:</strong></p> <p>Regarding the question of how I'm using Emacs. Yes, I start Emacs, then enter slime with M-x slime. I read that I could get proper syntax highlighting by next entering lisp mode with M-x lisp-mode.</p> <p>It did provide syntax highlighting, but as pointed out below, it's meant for editing text files, not interacting with the REPL.</p> <p>I also recently read that placing the following in my .emacs file will enable syntax highlighting (it did not work).</p> <pre><code>; Syntax Highlighting (global-font-lock-mode 1) ; Enable slime (add-to-list 'load-path "/home/doug/Software/slime/") ; your SLIME directory (setq inferior-lisp-program "/home/doug/Software/ccl/ccl") ; your Lisp system (require 'slime) (slime-setup) ; Enable psvn (require 'psvn) </code></pre> <p>So I guess my question needs revising. Since lisp-mode isn't meant to simply enable lisp features for slime, then how I enable syntax highlighting in slime?</p> <p><strong>Edit 2:</strong></p> <p>The answer was provided in a comment.</p> <p>Start slime then open/create a new file to work with. This is the buffer where lisp-mode is intended to be used.</p> <p>The function is written, highlighted, and sent to the REPL. The output appears at the bottom.</p> <p>The two are supposed to cooperate, not integrate.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload