1 @node Installation, The REPL, Introduction, Top
10 @node Must needs, Setting it up, Installation, Installation
13 @cindex supported versions
14 @cindex versions supported
15 If Geiser came with any guarantees, you'd break all of them by not using
16 GNU Emacs @value{EMACS_VERSION} (or better: i regularly use it with a
17 recent Emacs snapshot) and at least one of the supported Schemes,
22 @uref{http://www.racket-lang.org, Racket} @value{RACKET_VERSION} or better
24 @uref{http://www.gnu.org/software/guile, Guile} @value{GUILE_VERSION} or
28 Since Geiser supports multiple REPLs, having both of them will just add
31 @subsubheading Downloading Geiser
33 @cindex use the source, Luke
34 You'll also need Geiser itself. The latest release tarball can be found
35 @downfile{, here}, while older versions are @uref{@value{DOWN_BASE}/,
36 here}. Just download @downfile{@value{TARBALL}, @value{TARBALL}}
37 and untar it in a directory of your choice.
39 If you feel like living on the bleeding edge, just grab Geiser from its
40 Git repository @uref{http://git.savannah.nongnu.org/cgit/geiser.git/, over
41 at Savannah}, either with the following incantation:
44 git clone git://git.sv.gnu.org/geiser.git
47 @noindent or, if you happen to live behind a firewall, with the alternative:
50 git clone http://git.sv.gnu.org/r/geiser.git
54 You can also follow Geiser's development in
55 @uref{https://github.com/jaor/geiser, one}
56 @uref{http://repo.or.cz/w/geiser.git, or}
57 @uref{http://gitorious.org/geiser, three} mirrors that are kept
58 synchronized with the one at Savannah.
60 Either way, you'll now be in possession of a copy of Geiser's libre
61 code. I'll follow you into its directory and the next section.
63 @node Setting it up, Friends, Must needs, Installation
64 @section Setting it up
66 Geiser is ready to be used out of the box without much more ado. For the
67 sake of concreteness, let's assume you put its source in the directory
68 @file{~/lisp/geiser}. All you need to do is to add the following
69 line to your Emacs initialisation file (be it @file{~/.emacs} or any of
70 its moral equivalents):
73 (load-file "~/lisp/geiser/elisp/geiser.el")
77 or simply evaluate that form inside Emacs (you wouldn't kill a friend
78 just to start using Geiser, would you?). That's it: you're ready to
80 @ref{quick-start,,go}.
83 go (@pxref{The REPL}).
87 If you obtained the Geiser source tree from a release tarball, you can
88 even continue to read this fine manual inside Emacs by opening
89 @file{doc/geiser.info} using @kbd{C-u C-h i}. The manual is also
90 available in PDF format @downfile{geiser-manual-@value{VERSION}.pdf,
94 @cindex byte-compilation
95 What? You still here? I promise the above is all that's needed to start
96 using Geiser. But, in case you are missing your @t{configure/make all
97 install} routine, by all means, you can go through those motions to byte
98 compile and install Geiser too. That is, you enter the source directory
99 and (since we grabbed the development tree) run the customary
108 I recommend that you compile Geiser in a separate directory:
111 $ mkdir build && cd build
118 Now you have two options: loading the byte-compiled Geiser from the
119 @file{elisp} subdirectory, or installing it system-wide. To load the
120 byte-code from here, add this line to your initialisation file:
123 (load "~/lisp/geiser/build/elisp/geiser-load")
127 and eval that form and you're done (you could also restart Emacs, but
128 killing your friends is widely considered bad form). Yes, that's
129 @code{load} and @file{geiser-load} instead of @code{load-file} and
132 If you prefer a system-wide installation, just type:
138 With the above spell, Geiser will be compiled and installed in a safe
139 place inside Emacs load path. To load it into Emacs you'll need,
140 @i{instead} of the @code{load-file} form above, the following line in
141 your initialisation file:
144 (require 'geiser-install)
148 Please note that we're requiring @code{geiser-install}, and @i{not}
149 @code{geiser}, and that there's no @code{load-file} to be seen this
150 time. There are some ways of fine-tuning this process, mainly by
151 providing additional arguments in the call to @t{configure}: you'll find
152 those gory details in the file called @file{INSTALL}, right at the root
153 of the source tree. The installation will also take care of placing this
154 manual, in Info format, where Emacs can find it, so you can continue to
155 learn about Geiser inside its natural habitat. See you there and into
158 @node Friends, , Setting it up, Installation
161 Although Geiser does not need them, it plays well with (and is enhanced
162 by) the following Emacs packages:
168 @item @uref{http://www.emacswiki.org/emacs/ParEdit, Paredit}.
170 Regardless of whether you use Geiser or not, you shouldn't be coding
171 in any Lisp dialect without the aid of Taylor Campbell's structured
173 @item @uref{http://nschum.de/src/emacs/company-mode/, Company}.
174 Nikolaj Schumacher's @code{company-mode} provides a generic front-end
175 for completion engines (such as Geiser's). Very nice if you like that
176 kind of thing: judge by yourself with the help of
177 @uref{http://www.screentoaster.com/watch/stU0lSRERIR1pYRFVdXVlRVFFV/company_mode_for_gnu_emacs,
179 @item @uref{http://www.neilvandyke.org/quack/, Quack}.
180 You can still use the many goodies provided by Neil van Dyke's
181 @code{quack-mode}, since most of them are not (yet) available in Geiser.
182 The only caveat might be a conflict between Quack's and Geiser's default
183 key bindings, which i'm sure you'll manage to tackle just fine. It's
184 also probably a good idea to require @code{quack} @i{after} loading
185 @file{geiser.el} (or requiring a compiled version).
189 You just need to install and setup them as usual, for every package's
190 definition of usual. Geiser will notice their presence and react
195 @c TeX-master: "geiser"