Skip to content
Snippets Groups Projects
Verified Commit d338e452 authored by "the Phoeron" Colin J.E. Lupton's avatar "the Phoeron" Colin J.E. Lupton
Browse files

Clean up inline hints in Ex 1.1.8

parent e19c9502
No related branches found
No related tags found
No related merge requests found
......@@ -16,11 +16,9 @@ To continue with this book, however, you will need to install Common Lisp on you
Steel Bank Common Lisp is one of the easiest Lisp implementations to get up and running—it has out of the box support for a wide selection of platforms, and is considered to be the most robust implementation available. Since it automatically compiles everything you enter at the REPL, your running Lisp processes also benefit from a major speed-boost over other Lisps.
<div class="alert alert-info">
<p>
<strong>Note:</strong> the SBCL REPL is minimal by design, since it is primarily used from within Emacs+SLIME which provides its own custom prompt, history, completion, multi-line editing capabilities, and more. In order to use it effectively straight from the command-line, you will need to install a separate tool on OS X and Linux called `rlwrap`, a readline wrapper. It provides evaluation history, multi-line editing, and can be configured for completions and filters. You can read more about `rlwrap` here: <a href="http://utopia.knoware.nl/~hlub/uck/rlwrap/" target="_blank">utopia.knoware.nl/~hlub/uck/rlwrap/</a>.
</p>
</div>
{% hint style='info' %}
The SBCL REPL is minimal by design, since it is primarily used from within Emacs+SLIME which provides its own custom prompt, history, completion, multi-line editing capabilities, and more. In order to use it effectively straight from the command-line, you will need to install a separate tool on OS X and Linux called `rlwrap`, a readline wrapper. It provides evaluation history, multi-line editing, and can be configured for completions and filters. You can read more about `rlwrap` here: https://github.com/hanslub42/rlwrap
{% endhint %}
#### Windows
......@@ -97,11 +95,6 @@ You can put your Lisp projects under `~/quicklisp/local-projects/` so that Quick
If you ask any Lisp developer what editor you should be using, or what IDE is available for Common Lisp, the first thing they'll tell you is, Emacs. Emacs and SLIME (the Superior Lisp Interaction Mode for Emacs), makes a powerful combination. You can control the entire environment with your keyboard, never having to waste time reaching for the mouse; run, test, and debug code in the REPL as you write it in another buffer; experiment and explore alternate approaches to solving the same problem, profiling your code to get the best performance; and have the full Common Lisp HyperSpec at your fingertips. The only problem is, some users really dislike Emacs, or simply don't know it. The steep learning curve can be a real damper to your progress when coming to both Lisp and Emacs as a newbie; so the policy of this book is, use what you know, and make it work until you know Lisp well enough to get comfortable learning Emacs. If you wait until the right time, learning Emacs will be a boost to your productivity, not a hindrance.
<div class="alert alert-info">
<strong>Note:</strong>
<p>If you want to move ahead with Emacs, detailed instructions for setting up the Emacs Live environment with support for Common Lisp are available in the next chapter, your first Extra Credit exercise.</p>
</div>
If you know Emacs and have a great disdain for it, far preferring Vim, you can take advantage of most of the features of SLIME through the Vim package, Slimv.
For users who have no experience with Emacs or Vim, all you really need at the moment is a simple text editor. Anything more will probably just confuse you, and keep you from focusing on Lisp itself. A few worth checking out are:
......
# CHANGELOG
## 2022-08-25
- Exercise 1.1.8, "Configuring Your Development Environment"
- Clean-up inline hints
## 2022-08-24
- Add book.json to manually define GitBook configuration and fix some outstanding oddities
......
0% Loading or .
You are about to add 0 people to the discussion. Proceed with caution.
Finish editing this message first!
Please register or to comment