SLIME User Manual - Common Lisp.net

More documents

Recommendations

Info

Chapter 7: Customization 19:SPAWNThis style uses multiprocessing support in the Lisp system to execute eachrequest in a separate thread. This style has similar properties to :SIGIO, butit does not use signals and all requests issued by Emacs can be executed inparallel.The default request handling style is chosen according to the capabilities your Lispsystem. The general order of preference is :SPAWN, then :SIGIO, then :FD-HANDLER. Youcan check the default style by calling SWANK-BACKEND:PREFERRED-COMMUNICATION-STYLE.You can also override the default by setting SWANK:*COMMUNICATION-STYLE* in your Swankinit file.7.2.2 Other configurablesTo use the sldb debugger globally for all debugging in the Lisp system you can add thisline to your init file:(setq *debugger-hook* #’swank:swank-debugger-hook)You can also modify these Swank variables:SWANK:*CONFIGURE-EMACS-INDENTATION*This variable controls whether indentation styles for &body-arguments in macrosare discovered and sent to Emacs. It is enabled by default.SWANK:*GLOBALLY-REDIRECT-IO*When true this causes the standard streams (*standard-output*, etc) to beglobally redirected to the repl in Emacs. When NIL (the default) these streamsare only temporarily redirected to Emacs using dynamic bindings while handlingrequests. Note that *standard-input* is currently never globally redirectedinto Emacs, because it can interact badly with the Lisp’s native replby having it try to read from the Emacs one.SWANK:*SLDB-PPRINT-FRAMES**PRINT-PRETTY* is bound to this value while formatting backtraces in sldb.The default value is NIL.SWANK:*USE-DEDICATED-OUTPUT-STREAM*This variable controls an optimization for sending printed output from Lisp toEmacs. When t (the default) a separate socket is established solely for Lisp tosend printed output to Emacs through. Without the optimization it is necessaryto send output in protocol-messages to Emacs which must then be decoded, andthis doesn’t always keep up if Lisp starts “spewing” copious output.SWANK:*LOG-EVENTS*Setting this variable to t causes all protocol messages exchanged with Emacsto be printed to *TERMINAL-IO*. This is useful for low-level debugging and forobserving how slime works “on the wire.” The output of *TERMINAL-IO* canbe found in your Lisp system’s own listener, usually in the buffer *inferiorlisp*.
Chapter 8: Credits 208 CreditsThe soppy ending...Hackers of the good hackslime is an Extension of slim by Eric Marsden. At the time of writing, the authors andcode-contributors of slime are:Helmut Eller Luke Gorrie Marco BaringerDaniel Barlow Alan Ruttenberg Wolfgang JenknerPeter Seibel Lawrence Mitchell Christophe RhodesBill Clementson Michael Weber James BielmanEdi Weitz Brian Downing Thomas F. BurdickAlan Shutko Tiago Maduro-Dias Robert E. BrownMatthew Danish Martin Simmons Lars Magne IngebrigtsenJouni K Seppanen Eric Blood Bjørn NordbøAndras Simon Zach Beane Thomas SchillingSean O’Rourke Robert Lehr Raymond ToyPawel Ostrowski Lasse Rasinen Julian StecklinaIvan Boldyrev Ignas Mikalajunas Hannu KoivistoFrederic Brunel Bryan O’Connor Brian MastenbrookBarry FishmanAndreas Fuchs... not counting the bundled code from ‘hyperspec.el’, CLOCC, and the CMU AIRepository.Many people on the slime-devel mailing list have made non-code contributions toslime. Life is hard though: you gotta send code to get your name in the manual. :-)Thanks!We’re indebted to the good people of common-lisp.net for their hosting and help, and forrescuing us from “Sourceforge hell.”Implementors of the Lisps that we support have been a great help. Thanks to thecmucl maintainers on the cmucl-imp list, Dan Barlow 1 and Christophe Rhodes of sbcl,Gary Byers of OpenMCL, Martin Simmons of LispWorks (generously sponsored by AlainPicard of Memetrics), Peter Graves of abcl, and to Craig Norvell and Kevin Layer of Franz.1 Dan is one of “us”, so naturally these thanks apply to the sbcl-hacker side of his personality.
Page 1 and 2: SLIME User ManualThe Superior Lisp
Page 4 and 5: Chapter 1: Introduction 11 Introduc
Page 6 and 7: Chapter 2: Getting started 32.2.2 C
Page 8 and 9: Chapter 3: slime-mode 5using the in
Page 10 and 11: Chapter 3: slime-mode 7C-c C-d hC-c
Page 12 and 13: Chapter 3: slime-mode 9RETdlnqslime
Page 14 and 15: Chapter 4: REPL: the “top level
Page 16 and 17: Chapter 5: SLDB: the SLIME debugger
Page 18 and 19: Chapter 6: Extras 156 Extras6.1 sli
Page 20 and 21: Chapter 7: Customization 177 Custom

SLIME User Manual - Common Lisp.net

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?