Index: slime/ChangeLog diff -u slime/ChangeLog:1.1678 slime/ChangeLog:1.1682 --- slime/ChangeLog:1.1678 Wed Feb 11 20:55:01 2009 +++ slime/ChangeLog Sat Feb 14 17:01:52 2009 @@ -1,3 +1,30 @@ +2009-02-14 Tobias C. Rittweiler tcr@freebits.de + + * slime.el (slime-reader-conditionals-regexp): New variable. Taken + from `slime-forward-reader-conditional'. + (slime-pretty-package-name): Fix modeline display for buffer + containing forms like (in-package "#+foo :A #-foo :B"). Also do + not call `read' on the name; the function does not need to return + a symbol, and `read' may choke on non-elisp syntax. + +2009-02-14 Helmut Eller heller@common-lisp.net + + Don't signal conditions in interrupt handler to + avoid problems with naive code like + (handler-case foo (condition bar)) + + * swank-backend.lisp (*interrupt-queued-handler*): Use a dynamic + variable instead. + (slime-interrupt-queued): Deleted. + * swank-cmucl.lisp, swank.lisp: Ditto. + +2009-02-14 Helmut Eller heller@common-lisp.net + + * slime.el (slime-restart-or-init-modeline-update-timer): Don't + run the timer repeatedly. + (slime-change-directory): Also change the directory in the + connection-buffer. + 2009-02-11 Tobias C. Rittweiler tcr@freebits.de
* slime.el (slime-current-tlf, slime-current-form-path): New Index: slime/contrib/ChangeLog diff -u slime/contrib/ChangeLog:1.173 slime/contrib/ChangeLog:1.174 --- slime/contrib/ChangeLog:1.173 Mon Feb 2 18:55:36 2009 +++ slime/contrib/ChangeLog Sat Feb 14 12:59:32 2009 @@ -1,3 +1,7 @@ +2009-02-14 Helmut Eller heller@common-lisp.net + + * swank.rb: New file. + 2009-02-02 Tobias C. Rittweiler tcr@freebits.de
* swank-arglists.lisp (arglist-for-echo-area): Bleh, can't use
On Sun, 15 Feb 2009, Helmut Eller wrote:
+2009-02-14 Helmut Eller heller@common-lisp.net
- swank.rb: New file.
I'm not sure where (or how far) you want to take it, but this looks like very good news to me! Is it ready for alpha-testing? I.e., are you ready for taking questions and bug reports from clueless users?
Andras
* Andras Simon [2009-02-19 14:01+0100] writes:
I'm not sure where (or how far) you want to take it, but this looks like very good news to me! Is it ready for alpha-testing?
If you want to use it, you have to fill in many missing parts.
This was primarily a exercise to learn a bit of Ruby. The file implements only very little functionality. The only command that works is slime-eval-region. The debugger isn't a real debugger it just displays the backtrace (without local variables) from the exception object.
Certain commands, like slime-eval-last-expression, would need some elisp code which understands Ruby's syntax a bit better. Or perhaps it would be better to have different commands like eval-current-line because "the last expression" is not a very useful concept in a infix syntax.
I.e., are you ready for taking questions and bug reports from clueless users?
I can answer questions, but I don't have a good idea how a decent Slime-for-Ruby should look like. E.g. tab-completion for method-names seems to be hard(er) to implement in Ruby because most names are interpreted relative to some module/class while in Lisp most function-names are global symbols.
My impression was that Emacs's ruby-mode works quite well with irb in a comint buffer and hence, something like Slime is less necessary. I was also pleasantly surprised that Matz seems to be one of the authors of ruby-mode.
Helmut.
On Thu, 19 Feb 2009, Helmut Eller wrote:
- Andras Simon [2009-02-19 14:01+0100] writes:
I'm not sure where (or how far) you want to take it, but this looks like very good news to me! Is it ready for alpha-testing?
If you want to use it, you have to fill in many missing parts.
I wish I could...
This was primarily a exercise to learn a bit of Ruby. The file implements only very little functionality. The only command that works is slime-eval-region. The debugger isn't a real debugger it just displays the backtrace (without local variables) from the exception object.
Certain commands, like slime-eval-last-expression, would need some elisp code which understands Ruby's syntax a bit better. Or perhaps it would be better to have different commands like eval-current-line because "the last expression" is not a very useful concept in a infix syntax.
Syntax-related stuff could perhaps be lifted from ruby-mode. Although I'm not sure how good that is; ruby-forward-sexp for example doesn't quite do what I think it should. (But it's possible that the problem lies with my expectations.)
I.e., are you ready for taking questions and bug reports from clueless users?
I can answer questions, but I don't have a good idea how a decent Slime-for-Ruby should look like. E.g. tab-completion for method-names seems to be hard(er) to implement in Ruby because most names are interpreted relative to some module/class while in Lisp most function-names are global symbols.
I wish I knew how to go about it. Maybe a combination of slime and jde (very fancy java mode for emacs) would be needed. (It's been a while, but I think it could do completion.) BTW it seems that ruby-mode can already do some symbol-completion based on ri:
http://groups.google.com/group/comp.lang.ruby/browse_thread/thread/50a36818c...
Of course it's not the real thing.
My impression was that Emacs's ruby-mode works quite well with irb in a comint buffer and hence, something like Slime is less necessary. I was also pleasantly surprised that Matz seems to be one of the authors of ruby-mode.
I'm afraid I'm spoiled by slime. ruby-mode is much better than nothing, but much less capable than ilisp was. But it's possible that I'm missing something.
Thanks! Andras
-
Andras Simon -
Helmut Eller