Skip to content

Improve Emacs instructions, point users to an emacs quickstart. #524

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 3 commits into from
Jan 22, 2024
Merged
Show file tree
Hide file tree
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 2 additions & 0 deletions editor-support.md
Original file line number Diff line number Diff line change
Expand Up @@ -29,6 +29,7 @@ Since SLIME is heavily modular and the defaults only do the bare minimum (not
even the SLIME REPL), you might want to enable more features with

~~~lisp
(require 'slime)
(slime-setup '(slime-fancy slime-quicklisp slime-asdf))
~~~

Expand All @@ -41,6 +42,7 @@ Now you can run SLIME with `M-x slime` and/or `M-x slime-connect`.
See also:

* [https://wikemacs.org/wiki/SLIME](https://wikemacs.org/wiki/SLIME) - configuration examples and extensions.
* [https://github.com/susam/emacs4cl](https://github.com/susam/emacs4cl) - a minimal Emacs configuration to get new users up and running quickly, *with* a tutorial.


### Using Emacs as an IDE
Expand Down
2 changes: 2 additions & 0 deletions os.md
Original file line number Diff line number Diff line change
Expand Up @@ -51,6 +51,8 @@ NIL

You should also note that some of these implementations also provide the ability to _set_ these variables. These include ECL (`si:setenv`) and AllegroCL, LispWorks, and CLISP where you can use the functions from above together with [`setf`](http://www.lispworks.com/documentation/HyperSpec/Body/m_setf_.htm). This feature might be important if you want to start subprocesses from your Lisp environment.

To set an envionmental variable, you can `setf` with `(uiop:getenv "lisp")` in a implementation-independent way.

Also note that the
[Osicat](https://www.common-lisp.net/project/osicat/manual/osicat.html#Environment)
library has the method `(environment-variable "name")`, on POSIX-like
Expand Down