slime-devel

slime-devel@common-lisp.net

4231 discussions

[slime-devel] Daily ChangeLog diff
by Helmut Eller 20 Mar '10

20 Mar '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2036 slime/ChangeLog:1.2042 --- slime/ChangeLog:1.2036 Tue Mar 16 12:20:07 2010 +++ slime/ChangeLog Thu Mar 18 14:24:25 2010 @@ -1,3 +1,84 @@ +2010-03-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + Remove attach-gdb restart. Instead add SLDB shortcut `A'. + + * slime.el (slime-dispatch-event): Remove :gdb-attach. + (slime-attach-gdb): Changed API. Takes connection not pid now and + lightweight &optional arg. If not lightweight, get the default gdb + config from the inferior Lisp. + (sldb-break-with-system-debugger): New command, bound to `A' in + sldb. Called this way to mimick + `sldb-break-with-default-debugger', and because it may make sense + to go beyond gdb in future, e.g. to invoke the Java Debugger for + ABCL. + + * swank.lisp (call-with-gdb-restart, with-gdb-restart): Removed. + (with-top-level-restart): Remove use of with-gdb-restart. + (make-connection, start-server, create-server, setup-server): + Remove inferior-lisp flag again. Not needed anymore. + +2010-03-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + Add M-x slime-attach-gdb as an interactive function. + + The ATTACH-GDB restart is nice because it's convenient and the + backends can specify customized gdb configuration. + + Sometimes, if the Lisp is too screwed up, going over a restart + involving the SWANK middle layer may not be possible. For that, a + manual M-x slime-attach-gdb may come in handy. + + * slime.el (slime-read-connection): New helper. + (slime-attach-gdb): Use it. Make it an interactive function. + +2010-03-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (call-with-gdb-restart): Forgot to remove trailing T. + +2010-03-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (open-dedicated-output-stream): Forgot to rename + accept-authenticated-connection to accept-authenticated-client + here. + +2010-03-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + Add an ATTACH-GDB restart to SLDB. + + * swank.lisp (call-with-gdb-restart): New. Sends the new :gdb-attach event to Emacs. + (with-gdb-restart): Sugar. + (with-top-level-restart): Also expand to with-gdb-restart. + (dispatch-event): Add :gdb-attach event. + + * swank-backend.lisp (gdb-initial-commands): New interface + function so backends can customize how gdb needs to be configured + for their implementation. + + * swank-ecl.lisp (gdb-initial-commands): Implement. + + * slime.el (slime-dispatch-event): Add clause for :gdb-attach. + (slime-attach-gdb): New. + +2010-03-18 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank.lisp (connection): Add socket slot, make socket-io slot + not be required to be filled in during object creation. Add + inferior-lisp slot so we can know whether a connection belongs to + a superior Emacs process. Need for that will come in following + commit. + (make-connection): Our constructor. + (create-connection): Removed; not needed anymore. + (finish-connection-setup): Function to fill socket-io slot. + (start-server): Results in inferior-lisp slot being T. + (create-server): Results in inferior-lisp slot being NIL. + (setup-server): Adapted accordingly. Construct connection early so + we do not have to pass down all the meta information explicitly. + (serve-connection): Adapted accordingly. + (accept-authenticated-client): Renamed from + accept-authenticated-connection. + (dispatch-event): Get rid of unused :%apply and :end-of-stream + events. + 2010-03-16 Tobias C. Rittweiler <tcr(a)freebits.de> * swank-ecl.lisp (source-location): Also return EXT::FOO as

3 4

[slime-devel] Daily ChangeLog diff
by Helmut Eller 20 Mar '10

20 Mar '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2042 slime/ChangeLog:1.2043 --- slime/ChangeLog:1.2042 Thu Mar 18 14:24:25 2010 +++ slime/ChangeLog Fri Mar 19 08:32:30 2010 @@ -1,3 +1,18 @@ +2010-03-19 Tobias C. Rittweiler <tcr(a)freebits.de> + + * slime.el (slime-lisp-implementation-program): New connection + variable. + (slime-set-connection-info): Adapted to set it. + (slime-attach-gdb): Use it to invoke gdb so gdb is able to find + debugging symbols on non-Linux platforms. + + * swank.lisp (connection-info): Include lisp-implementation-program. + + * swank-backend.lisp (lisp-implementation-program): New interface. + Default implementation based on command-line-args. + + * swank-ecl.lisp (command-line-args): Implement. + 2010-03-18 Tobias C. Rittweiler <tcr(a)freebits.de> Remove attach-gdb restart. Instead add SLDB shortcut `A'. @@ -45,7 +60,8 @@ Add an ATTACH-GDB restart to SLDB. - * swank.lisp (call-with-gdb-restart): New. Sends the new :gdb-attach event to Emacs. + * swank.lisp (call-with-gdb-restart): New. Sends the new + :gdb-attach event to Emacs. (with-gdb-restart): Sugar. (with-top-level-restart): Also expand to with-gdb-restart. (dispatch-event): Add :gdb-attach event.

1 0

[slime-devel] (:end-of-stream) clause in dispatch-event
by Tobias C. Rittweiler 19 Mar '10

19 Mar '10

Grepping for :end-of-stream only reveals that use in dispatch-event. Same for %apply. Any problem with getting rid of those? -T.

3 4

Re: [slime-devel] CVS slime
by Helmut Eller 18 Mar '10

18 Mar '10

* CVS User trittweiler [2010-03-18 16:59+0100] writes: > Update of /project/slime/cvsroot/slime > In directory cl-net:/tmp/cvs-serv19810 > > Modified Files: > ChangeLog slime.el > Log Message: > Add M-x slime-attach-gdb as an interactive function. > > The ATTACH-GDB restart is nice because it's convenient and the > backends can specify customized gdb configuration. Is there a technical reason that the restart must be there or is it a time limited advertising campaign? Helmut

3 6

[slime-devel] [2nd CfP] 7th European Lisp Workshop at ECOOP'10, June 21/22
by Didier Verna 17 Mar '10

17 Mar '10

+------------------------------------------------------------+ | 2ND CALL FOR PAPERS | | 7th European Lisp Workshop | | June 21/22, Maribor, Slovenia - co-located with ECOOP 2010 | +------------------------------------------------------------+ News ==== Our invited speaker, Manuel Serrano, will talk about "diffuse programming" and HOP. The abstract of his presentation can be found on the website at: http://european-lisp-workshop.org/upcoming/programme.php Important Dates =============== Submission deadline: April 19, 2010 Notification of acceptance: May 05, 2010 ECOOP early registration deadline: May 10, 2010 7th European Lisp Workshop: June 21 or 22, 2010 (tbdl) Please note that registration must be done with ECOOP itself. For more information visit http://www.european-lisp-workshop.org Contact: Didier Verna, didier(a)lrde.epita.fr Invited Speaker =============== Manuel Serrano (INRIA, France) http://www-sop.inria.fr/members/Manuel.Serrano/ Overview ======== "...Please don't assume Lisp is only useful for Animation and Graphics, AI, Bio-informatics, B2B and E-Commerce, Data Mining, EDA/Semiconductor applications, Expert Systems, Finance, Intelligent Agents, Knowledge Management, Mechanical CAD, Modeling and Simulation, Natural Language, Optimization, Research, Risk Analysis, Scheduling, Telecom, and Web Authoring just because these are the only things they happened to list." -- Kent Pitman Lisp, one of the eldest computer languages still in use today, is gaining momentum again. The structure of Lisp makes it easy to extend the language or even to implement entirely new dialects without starting from scratch, making it the ideal candidate for writing Domain Specific Languages. Common Lisp, with the Common Lisp Object System (CLOS), was the first object-oriented programming language to receive an ANSI standard and remains the most complete and advanced object system of any programming language, while influencing many other object-oriented programming languages that followed. This workshop will address the near-future role of Lisp-based languages in research, industry and education. We solicit contributions that discuss the opportunities Lisp provides to capture and enhance the possibilities in software engineering. We want to promote lively discussion between researchers proposing new approaches and practitioners reporting on their experience with the strengths and limitations of current Lisp technologies. The workshop will have two components: there will be formal talks, and interactive turorial/demo/coding sessions. Papers ====== Formal presentations in the workshop should take between 20 minutes and half an hour; additional time will be given for questions and answers. Suggested topics include (but are not limited to): - Context-, aspect-, domain-oriented and generative programming - Macro-, reflective-, meta- and/or rule-based development approaches - Protocol meta-programming and libraries - New language features and abstractions - Software evolution - Development aids - Persistent systems - Dynamic optimization - Implementation techniques - Hardware Support - Efficiency, distribution and parallel programming - Educational approaches and perspectives - Experience reports and case studies Interactive Tutorial/Demo/Coding Sessions ========================================= Additionally, we invite less formal talks in the form of interactive tutorial/demo/coding sessions. The purpose of these sessions is both to demonstrate and receive feedback on any interesting Lisp system, either stable or under development. Being less formal than technical paper presentations, these sessions are expected to be highly interactive. Submission Guidelines ===================== Potential contributors are encouraged to submit: - a long paper (around 10 pages) presenting scientific and/or empirical results about Lisp-based uses or new approaches for software engineering purposes, - a short essay (5 pages) defending a position about where research, practice or education based on Lisp should be heading in the near future, - a proposal for an interactive tutorial/demo/coding session (1-2 pages) describing the involved library or application, and the subject of the session. Papers (both long and short) should be formatted following the ACM SIGS guidelines and include ACM classification categories and terms (see below). Authors will later be required to sign an ACM copyright form, as the workshop proceedings will be published in the ACM Digital Library. For more information on the submission guidelines and the ACM keywords, see: http://www.acm.org/sigs/publications/proceedings-templates http://www.acm.org/about/class/1998 Submissions should be uploaded to Easy Chair, at the following address: http://www.easychair.org/conferences/?conf=elw2010 Organizers ========== Didier Verna, EPITA Research and Development Laboratory, Paris Charlotte Herzeel, Programming Technology Lab, Vrije Universiteit, Brussel Robert Strandh, LaBRI, University of Bordeaux 1, France Christophe Rhodes, Goldsmiths College, University of London -- Resistance is futile. You will be jazzimilated. Scientific site: http://www.lrde.epita.fr/~didier Music (Jazz) site: http://www.didierverna.com

1 0

[slime-devel] Daily ChangeLog diff
by Helmut Eller 17 Mar '10

17 Mar '10

Index: slime/ChangeLog diff -u slime/ChangeLog:1.2035 slime/ChangeLog:1.2036 --- slime/ChangeLog:1.2035 Thu Mar 11 04:05:50 2010 +++ slime/ChangeLog Tue Mar 16 12:20:07 2010 @@ -1,3 +1,10 @@ +2010-03-16 Tobias C. Rittweiler <tcr(a)freebits.de> + + * swank-ecl.lisp (source-location): Also return EXT::FOO as + candidate to search through the TAGS file because SI and EXT both + name the same package, and in ECL's code base, sometimes the + former, sometimes the latter is used. + 2010-03-10 Tobias C. Rittweiler <tcr(a)freebits.de> * swank.lisp (signal-interrupt): Removed.

1 0

[slime-devel] PATCH: Improving interaction with other systems
by Andrey Moskvitin 13 Mar '10

13 Mar '10

Hi, Now Hunchentoot included the following code: (when (find-package :swank) (ignore-errors (eval `(,(find-symbol (string '#:add-hook) :swank) ,(find-symbol (string '#:*connection-closed-hook*) :swank) 'after-close-swank-connection)))) This does not seem reliable, but is absolutely necessary for a more safe debugging remote servers. I propose a patch that will rewrite this code more natural way: #+swank(swank:add-hook swank:*connection-closed-hook* 'after-close-swank-connection) See attachment. Moskvitin Andrey

2 1

[slime-devel] Daily ChangeLog diff
by Helmut Eller 13 Mar '10

13 Mar '10

Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.356 slime/contrib/ChangeLog:1.358 --- slime/contrib/ChangeLog:1.356 Tue Mar 9 18:26:23 2010 +++ slime/contrib/ChangeLog Fri Mar 12 22:08:04 2010 @@ -1,3 +1,13 @@ +2010-03-13 Stas Boukarev <stassats(a)gmail.com> + + * slime-asdf.el: use slime-from-lisp-filename so that slime-tramp can work. + Reported by Peter Stirling. + +2010-03-12 Stas Boukarev <stassats(a)gmail.com> + + * swank-arglists.lisp (extract-local-op-arglists (eql 'labels)): + Fix (labels ((name |))). + 2010-03-09 Stas Boukarev <stassats(a)gmail.com> * swank-arglists.lisp (arglist-ref): Don't error if a &key name isn't

1 0

[slime-devel] slime-asdf
by Peter Stirling 12 Mar '10

12 Mar '10

I read about the new "open-system" repl-command on [1], but found it doesn't support slime-tramp for cross-machine editing (it tries to open the files as if they were on the slime-client machine and not use scp to get the files from the machine with the swank-server). I think the attached patch performs the correct incantation, (it works for me anyway). [1] http://planet.lisp.org/

2 1

[slime-devel] Multiple REPLs
by Sebastian Tennant 12 Mar '10

12 Mar '10

Hi all, In buffer *Slime Connections* the marked entry is the 'default' REPL. What's the significance of 'default' status? Is it that in the case of multiple REPLS on a single lisp instance, it determines which REPL receives the lisp output? And if the above thinking is correct, does it have any significance at all when each REPL is on a separate lisp instance? Regards, Seb -- Emacs' AlsaPlayer - Music Without Jolts Lightweight, full-featured and mindful of your idyllic happiness. http://home.gna.org/eap

3 3

Jump to page:

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

slime-devel