On Wed, Dec 9, 2009 at 10:39 PM, Feng wrote:
>
>
> On Dec 7, 9:39 pm, David Nolen wrote:
>> http://github.com/jochu/swank-clojure/blob/master/src/main/clojure/sw...
>>
>> Is the offending line.
>
> It's really hard to reason about it in clojure source code. I see, in
> jswat debbuger, the root ca
You don't have the locals clearing changes Richard.
Rich Hickey, I confirm that this also causes an NPE on my setup.
Clojure new branch 6d40a76e8a012909f2d2a594ce66a78318889799
OS X 10.6 JDK 1.6 64bit
David
On Wed, Dec 9, 2009 at 10:46 PM, Richard Newman wrote:
> Does not happen for me throug
Does not happen for me through Slime or raw REPL.
user> (ns test.letfn)
(defn debug [n]
(letfn [(even [n]
(if (== n 0)
true
(odd (- n 1
(odd [n]
(if (== n 0)
false
(even (- n 1
On Dec 7, 9:39 pm, David Nolen wrote:
> http://github.com/jochu/swank-clojure/blob/master/src/main/clojure/sw...
>
> Is the offending line.
It's really hard to reason about it in clojure source code. I see, in
jswat debbuger, the root cause of NPE appears around byte code
(putfield ...) for a m
Yes, fuzzy-completion seems the only way to trigger it. For what it's
worth, it did not happen if reset to
commit a3e95cf5a72b22cd0728aba152d5f77603b722fc
Author: Rich Hickey
Date: Fri Dec 4 11:22:04 2009 -0500
update example in reify doc
- Feng
On Dec 7, 9:34 pm, David Nolen wrote:
>
http://github.com/jochu/swank-clojure/blob/master/src/main/clojure/swank/commands/contrib/swank_fuzzy.clj#L256
Is the offending line.
On Mon, Dec 7, 2009 at 9:34 PM, David Nolen wrote:
> Looking at the stacktrace it looks like this is because of swank_fuzzy.clj.
> I can start up the SLIME Repl
Looking at the stacktrace it looks like this is because of swank_fuzzy.clj.
I can start up the SLIME Repl no problem, I see your exact same stack trace
only if I try to trigger fuzzy completion via C-c TAB.
David
On Mon, Dec 7, 2009 at 9:24 PM, Feng wrote:
>
>
> On Dec 7, 8:57 pm, David Nolen
On Dec 7, 8:57 pm, David Nolen wrote:
> I was getting this as well, but this was before the last 3 commits to new.
> Did you wipe your old jars and class files and start afresh?
>
Yes, just to make sure not waste Rich's time. I did doubt and triple
checks, ant clean, find $HOME -name clojure\*.
I was getting this as well, but this was before the last 3 commits to new.
Did you wipe your old jars and class files and start afresh?
David
On Mon, Dec 7, 2009 at 8:31 PM, Feng wrote:
> Hi,
>
> After git pull on new branch
>
> commit 1da63ad10d2531264e86eb705a10b3cebc9b1067
> Author: Rich Hic
