diff --git a/doc/repl.texi b/doc/repl.texi index cfce6c8..e80aa08 100644 --- a/doc/repl.texi +++ b/doc/repl.texi @@ -2,7 +2,7 @@ @chapter The REPL @anchor{quick-start} If you've followed the indications in @ref{Setting it up}, your Emacs is -now ready to start playing. Otherwise, i'll wait for you: when you're +now ready to start playing. Otherwise, I'll wait for you: when you're ready, just come back here and proceed to the following sections. @menu @@ -18,7 +18,7 @@ ready, just come back here and proceed to the following sections. @section Starting the REPL @cindex REPL -To start a Scheme REPL (meaning, a scheme process offering you a +To start a Scheme REPL (meaning, a Scheme process offering you a Read-Eval-Print Loop), Geiser provides the generic interactive command @command{run-geiser}. If you run it (via, as is customary in Emacs, @kbd{M-x run-geiser}, you'll be saluted by a prompt asking which one of @@ -60,7 +60,7 @@ want to use the default. @cindex Racket's REPL server In Racket, you have to use the REPL server that comes with Geiser. To -that end, put Geiser's Racket scheme directory in the Racket's +that end, put Geiser's Racket Scheme directory in the Racket's collection search path and invoke @code{start-geiser} (a procedure in the module @code{geiser/server}) somewhere in your program, passing it the desired port. This procedure will start the REPL server in a @@ -80,9 +80,9 @@ Scheme process in a dedicated thread, meaning that your external program can go on doing whatever it was doing while you tinker with it from Emacs. Note, however, that all Scheme threads share the heap, so that you'll be able to interact with those other threads in the running -scheme from Emacs in a variety of ways. For starters, all your -(re)defintions will be visible everywhere. That's dangerous, but will -come in handy when you need to debug your running webserver. +Scheme from Emacs in a variety of ways. For starters, all your +(re)definitions will be visible everywhere. That's dangerous, but will +come in handy when you need to debug your running web-server. @cindex remote connections The connection between Emacs and the Scheme process goes over TCP, so it @@ -95,9 +95,9 @@ tunnel. @img{repl-menu, right} @cindex REPL commands A quick way of seeing what else Geiser's REPL can do for you, is to -display the corresponding entry up there in your menu bar. No, i don't +display the corresponding entry up there in your menu bar. No, I don't normally use menus either; but they can come in handy until you've -memorized Geiser's commands, as a learning device. And yes, i usually +memorized Geiser's commands, as a learning device. And yes, I usually run Emacs inside a terminal, but one can always use @uref{http://www.emacswiki.org/emacs/LaCarte, La Carte} to access the menus in a convenient enough fashion. @@ -111,7 +111,7 @@ is, they'll find the previous or next sexp that starts with the current input prefix (defined as the text between the end of the prompt and your current position, a.k.a. @dfn{point}, in the buffer). For going up and down the list unconditionally, just use @kbd{C-c M-p} and @kbd{C-c M-n}. -In addition, navigation is sexp- rather than line-based. +In addition, navigation is sexp-based rather than line-based. There are also a few commands to twiddle with the Scheme process. @kbd{C-c C-q} will gently ask it to quit, while @kbd{C-u C-c C-q} will @@ -142,7 +142,7 @@ will be happy to oblige. @cindex current module, change Once you enter a new module, only those bindings visible in its -namespace will be available to your evaluations. All schemes supported +namespace will be available to your evaluations. All Schemes supported by Geiser provide a way to import new modules in the current namespace. Again, there's a Geiser command, @command{geiser-repl-import-module}, to invoke such functionality, bound this time to @kbd{C-c C-i}. And, again, @@ -198,7 +198,7 @@ those questions too. Actually, if you've been playing with the REPL as you read, you might have notice some frantic activity taking place in the minibuffer every now and then. That was Geiser trying to be helpful (while, hopefully, -not being clippy), or, more concretely, what i call, for want of a +not being clippy), or, more concretely, what I call, for want of a better name, its @dfn{autodoc} mode. Whenever it's active (did you notice that @i{A} in the mode-line?), Geiser's gerbils will be scanning what you type and showing (unless you silent them with @kbd{C-c C-a}) @@ -243,7 +243,7 @@ If that's still not enough, Geiser can jump, via @kbd{M-.}, to the symbol's definition. A buffer with the corresponding file will pop up, with its point resting upon the identifier's defining form. When you're done inspecting, @kbd{M-,} will bring you back to where you were. As we -will see, these commands are also available in scheme buffers. @kbd{M-.} +will see, these commands are also available in Scheme buffers. @kbd{M-.} also works for modules: if your point is on an unambiguous module name, the file where it's defined will be opened for you. @@ -255,7 +255,7 @@ The looks and ways of the REPL can be fine-tuned via a bunch of customization variables. You can see and modify them all in the corresponding customization group (by using the menu entry or the good old @kbd{M-x customize-group geiser-repl}), or by setting them in your -Emacs initialization files (as a rule, all knobs in Geiser are turnable +Emacs initialization files (as a rule, all knobs in Geiser are tunable this way: you don't need to use customization buffers if you don't like them). @@ -275,7 +275,7 @@ forget about the richness of the Scheme ecosystem with something like @example (setq geiser-active-implementations '(racket)) @end example address@hidden in your initialisation files. address@hidden in your initialization files. @cindex scheme binary @cindex scheme executable path @@ -289,10 +289,10 @@ full path to the requisite binary. @cindex scheme init file @cindex GUILE_LOAD_PATH @cindex PLTCOLLECTS -You can also specify a couple more initialisation parameters. For Guile, +You can also specify a couple more initialization parameters. For Guile, @code{geiser-guile-load-path} is a list of paths to add to its load path when it's started, while @code{geiser-guile-init-file} is the path to an -initialisation file to be loaded on startup. The equivalent variables +initialization file to be loaded on start-up. The equivalent variables for Racket are @code{geiser-racket-collects} and @code{geiser-racket-init-file}. @@ -319,16 +319,16 @@ If you happen to love peace and quiet and prefer to keep your REPL's echo area free from autodoc's noise, @code{geiser-repl-autodoc-p} is the customization variable for you: set it to @code{nil} and autodoc will be disabled by default in new REPLs. You can always bring the fairies -back, on a per REPL basis, using @kbd{C-c C-a}. +back, on a per-REPL basis, using @kbd{C-c C-a}. @subsubheading Remote connections @cindex port, default @cindex host, default When using @code{connect-to-guile} or @code{geiser-connect}, you'll be -prompted for a host and a port, defaulting to localhost and 37146. You +prompted for a host and a port, defaulting to ``localhost'' and 37146. You can change those defaults customizing @code{geiser-repl-default-host} -and @code{geiser-repl-default-port}, respectfully. +and @code{geiser-repl-default-port}, respectively. @c Local Variables: @c mode: texinfo