Now that's interesting. It may be easier to share code because you too decided to not follow slime/swank which, I guess, imposes as a middle language something closer to emacs-lisp than to clojure for the exchanged data structures.
And we could indeed also share the whole code of the server side. I'm in the process of refactoring the code (client and server) for clojuredev. We have currently one single function, that returns a big map with all the information for the namespace. This has allowed me to do a namespace browser for clojuredev : http://code.google.com/p/clojure-dev/wiki/NamespaceBrowser -- Laurent On Jan 17, 8:53 pm, Meikel Brandmeyer <m...@kotka.de> wrote: > Hi, > > Am 17.01.2009 um 20:03 schrieb Matt Revelle: > > >> Tools such as SLIME and (I think) Gorilla, on the other hand, are not > >> written in language that makes sharing easy. > > > This is not entirely correct. SLIME works by communicating with the > > running Lisp process (in this case, Clojure), essentially all the > > integration between Emacs/SLIME and Clojure is written in Clojure. > > The component of SLIME that runs in the Lisp process is called SWANK. > > Yes. Gorilla also consists basically of some part on the Vim side, > which sends stuff to a Clojure server. That part is written in Clojure. > The result is sent back to Vim. > > So stuff like function completion etc. can be easily shared. > > Sincerely > Meikel > > smime.p7s > 5KViewDownload --~--~---------~--~----~------------~-------~--~----~ You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send email to clojure@googlegroups.com To unsubscribe from this group, send email to clojure+unsubscr...@googlegroups.com For more options, visit this group at http://groups.google.com/group/clojure?hl=en -~----------~----~----~----~------~----~------~--~---
