"Steven E. Harris" writes:
>> There was some discussion about it a couple months ago:
>
> I picked up the torch today, in hope that others will try again for a
> better resolution:
>
> http://thread.gmane.org/gmane.lisp.slime.devel/9178/focus=9383
Thanks for digging. I'll keep this around to s
Phil Hagelberg writes:
> There was some discussion about it a couple months ago:
I picked up the torch today, in hope that others will try again for a
better resolution:
http://thread.gmane.org/gmane.lisp.slime.devel/9178/focus=9383
--
Steven E. Harris
--
You received this message because
"Steven E. Harris" writes:
> Phil Hagelberg writes:
>
>> If someone would volunteer to fix it, I'd be thrilled. Nobody who is
>> interested in using CL and Clojure at the same time has stepped
>> forward so far, which is why it's currently broken.
>
> Can you characterize what needs to be fixed?
I've reverted to the setup that you listed, Ramakrishnan. I spent
quite a few hours trying to figure out how to use ELPA + the forked
slime + the new swank clojure, but failed miserably (despite the kind
assistance of Phil and others on another thread).
I would agree that it would be nice to have
On Fri, Jan 8, 2010 at 12:57 PM, Richard Newman wrote:
>> I don't want to have to use ELPA, or maven, or some other configuration
>> management thing to get basic tools like an editing environment for the
>> language up and running. Perhaps I should just bite the bullet and use the
>> crazy config
Phil Hagelberg writes:
> If someone would volunteer to fix it, I'd be thrilled. Nobody who is
> interested in using CL and Clojure at the same time has stepped
> forward so far, which is why it's currently broken.
Can you characterize what needs to be fixed?
--
Steven E. Harris
--
You receiv
I don't want to have to use ELPA, or maven, or some other
configuration management thing to get basic tools like an editing
environment for the language up and running. Perhaps I should just
bite the bullet and use the crazy configuration/package management
things that the clojure community
I agree with Steven on this. As one who uses emacs and SLIME for both common
lisp and clojure, I'd like to be able to use the current SLIME HEAD for clojure
development work. I consider the fact that swank-clojure and the SLIME HEAD
don't play nicely with each other to be a deficiency of swank-
"Steven E. Harris" writes:
>> Could you try installing SLIME via ELPA as recommended in the
>> swank-clojure readme?
>
> That will be a project I'll have to defer until the weekend, as I've
> never used ELPA. I use the CVS SLIME almost daily for Common Lisp work,
> so I'm reluctant to give it up.
Phil Hagelberg writes:
> Could you try installing SLIME via ELPA as recommended in the
> swank-clojure readme?
That will be a project I'll have to defer until the weekend, as I've
never used ELPA. I use the CVS SLIME almost daily for Common Lisp work,
so I'm reluctant to give it up. Also, it's n
"Steven E. Harris" writes:
> Here's the stack:
>
> o swank-clojure
> Git head.
>
> o SLIME
> Both CVS head and git://git.boinkor.net/slime.git head behave the same
> way, as the offending calls are in swank-clojure.
Could you try installing SLIME via ELPA as recommended in the
swank-clojur
Rob Wolfe writes:
> Do you use "slime-indentation.el" in your configuration?
Yes. It turns out that I have another Lisp-related initialization file
that contained the following form:
,
| (slime-setup '(slime-fancy
|slime-asdf
|slime-fontifying-fu
|
"Steven E. Harris" writes:
> "Steven E. Harris" writes:
>
>> Now get this: Right before the SLIME-Swank connection completes, Emacs
>> beeps and prints the following two lines in the *Messages* buffer:
>>
>> ,
>> | error in process filter: cond: etypecase failed: defun, (number cons
>> stri
"Steven E. Harris" writes:
> Now get this: Right before the SLIME-Swank connection completes, Emacs
> beeps and prints the following two lines in the *Messages* buffer:
>
> ,
> | error in process filter: cond: etypecase failed: defun, (number cons string)
> | error in process filter: etypecas
Rich Hickey writes:
> Perhaps it would be best to paste such dumps somewhere, rather than
> mail to the entire list?
I'll do that next time. Sorry for the noise.
--
Steven E. Harris
--
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this
> Perhaps it would be best to paste such dumps somewhere, rather than
> mail to the entire list?
Might I suggest
http://paste.lisp.org/
?
--
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
On Sat, Jan 2, 2010 at 11:03 AM, Steven E. Harris wrote:
> "Steven E. Harris" writes:
>
>> In the meantime, I'll continue the investigation.
>
> Here are two thread dumps of the Java process running Clojure and Swank,
> which, at this time, has a live Clojure REPL, but the Swank call to
> `connec
"Steven E. Harris" writes:
> In the meantime, I'll continue the investigation.
And yet more information: Apparently it's not critical to call on the
RuntimeMXBean#getName() method specifically to kick the Swank thread out
of its blocking call; just about /any call on a Java method/ from the
Cloj
"Steven E. Harris" writes:
> In the meantime, I'll continue the investigation.
Here are two thread dumps of the Java process running Clojure and Swank,
which, at this time, has a live Clojure REPL, but the Swank call to
`connection-info' hasn't completed yet.
This first one comes via jvisualvm:
Rob Wolfe writes:
> Unfortunately I have no idea what is the reason of this problem,
That makes two of us.
> but I'm curious what Java version are you using?
user=> (map #(System/getProperty %)
["java.version" "java.vendor" "java.vm.version"])
("1.6.0_17" "Sun Microsystems Inc." "1
"Steven E. Harris" writes:
[...]
> Here's the stack:
>
> o swank-clojure
> Git head.
>
> o SLIME
> Both CVS head and git://git.boinkor.net/slime.git head behave the same
> way, as the offending calls are in swank-clojure.
>
> o Clojure 1.1.0
> Downloaded Jar from code.google.com.
>
> o G
"Steven E. Harris" writes:
> it takes calling RuntimeMXBean#get() -- actually using the
> RuntimeMXBean instance -- to unblock the other thread.
I meant RuntimeMXBean#getName() there.
My typing is poor this morning.
--
Steven E. Harris
--
You received this message because you are subscribed
Phil Hagelberg writes:
> But I'm not quite following on the exact problem and specific repro
> case; could you clarify?
Yes. When I start SLIME, the Swank back-end starts and presents the
Clojure REPL in the *inferior-lisp* buffer. Right after that, the SLIME
front-end sends an "Emacs REX" comma
"Steven E. Harris" writes:
> Is there a separate mailing list to which I should report this problem?
There's http://groups.google.com/group/swank-clojure, though for this
particular issue you can just continue in this thread.
But I'm not quite following on the exact problem and specific repro
c
"Steven E. Harris" writes:
> My next step will be to instrument the Swank side to see when
> `connection-info' is being called.
I found the problem: swank.util.sys/get-pid.
It looks like the JMX call to get the PID hangs. If I visit the
*inferior-lisp* buffer's REPL and evaluate the following f
25 matches
Mail list logo
