After I upgrading to Leiningen 2.4.0, Ctrl-C causes an exception that 
throws me out to the shell, rather than bringing me back to the Leiningen 
prompt.  I just upgraded to 2.4.2 and still have the problem.  On another 
machine with an older Leiningen, I have no problem.  I suspect it's 
something about my configuration, or something I did wrong, since no one 
else has mentioned this issue in the group.  Maybe it's my Java 1.6?

In both cases, I upgraded with 'lein upgrade', and that seemed to go 
entirely smoothly.

A stacktrace is below.  Just to be sure, I created a new project with 'lein 
new' for this test.  ^C from a bare Leiningen prompt seems OK, but doing it 
while something's running (waiting for 'range' to finish, in this case) 
generates the problem. Any thoughts about what to investigate?  Thanks.

~/docs/src/clojure/foo$ uname -mprsv
Darwin 10.8.0 Darwin Kernel Version 10.8.0: Tue Jun  7 16:33:36 PDT 2011; 
root:xnu-1504.15.3~1/RELEASE_I386 i386 i386
~/docs/src/clojure/foo$ java -version
java version "1.6.0_65"
Java(TM) SE Runtime Environment (build 1.6.0_65-b14-462-10M4609)
Java HotSpot(TM) 64-Bit Server VM (build 20.65-b04-462, mixed mode)
~/docs/src/clojure/foo$ lein repl
nREPL server started on port 52556 on host 127.0.0.1 - 
nrepl://127.0.0.1:52556
REPL-y 0.3.1
Clojure 1.6.0
    Docs: (doc function-name-here)
          (find-doc "part-of-name-here")
  Source: (source function-name-here)
 Javadoc: (javadoc java-object-or-class-here)
    Exit: Control+D or (exit) or (quit)
 Results: Stored in vars *1, *2, *3, an exception in *e

user=> 22
22
user=> 

user=> (range 10000000000000)

user=> Exception in thread "Thread-5" clojure.lang.ExceptionInfo: 
Subprocess failed {:exit-code 130}
    at clojure.core$ex_info.invoke(core.clj:4403)
    at leiningen.core.eval$fn__4770.invoke(eval.clj:236)
    at clojure.lang.MultiFn.invoke(MultiFn.java:231)
    at leiningen.core.eval$eval_in_project.invoke(eval.clj:337)
    at clojure.lang.AFn.applyToHelper(AFn.java:160)
    at clojure.lang.AFn.applyTo(AFn.java:144)
    at clojure.core$apply.invoke(core.clj:626)
    at leiningen.repl$server$fn__8776.invoke(repl.clj:203)
    at clojure.lang.AFn.applyToHelper(AFn.java:152)
    at clojure.lang.AFn.applyTo(AFn.java:144)
    at clojure.core$apply.invoke(core.clj:624)
    at clojure.core$with_bindings_STAR_.doInvoke(core.clj:1862)
    at clojure.lang.RestFn.invoke(RestFn.java:425)
    at clojure.lang.AFn.applyToHelper(AFn.java:156)
    at clojure.lang.RestFn.applyTo(RestFn.java:132)
    at clojure.core$apply.invoke(core.clj:628)
    at clojure.core$bound_fn_STAR_$fn__4140.doInvoke(core.clj:1884)
    at clojure.lang.RestFn.invoke(RestFn.java:397)
    at clojure.lang.AFn.run(AFn.java:22)
    at java.lang.Thread.run(Thread.java:695)

SocketException The transport's socket appears to have lost its connection 
to the nREPL server
    clojure.tools.nrepl.transport/bencode/fn--5570/fn--5571 
(transport.clj:95)
    clojure.tools.nrepl.transport/bencode/fn--5570 (transport.clj:95)
    clojure.tools.nrepl.transport/fn-transport/fn--5544 (transport.clj:42)
    clojure.core/binding-conveyor-fn/fn--4145 (core.clj:1910)
    java.util.concurrent.FutureTask$Sync.innerRun (FutureTask.java:303)
    java.util.concurrent.FutureTask.run (FutureTask.java:138)
    java.util.concurrent.ThreadPoolExecutor$Worker.runTask 
(ThreadPoolExecutor.java:895)
    java.util.concurrent.ThreadPoolExecutor$Worker.run 
(ThreadPoolExecutor.java:918)
    java.lang.Thread.run (Thread.java:695)
Bye for now!

-- 
You received this message because you are subscribed to the Google
Groups "Clojure" group.
To post to this group, send email to [email protected]
Note that posts from new members are moderated - please be patient with your 
first post.
To unsubscribe from this group, send email to
[email protected]
For more options, visit this group at
http://groups.google.com/group/clojure?hl=en
--- 
You received this message because you are subscribed to the Google Groups 
"Clojure" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to