http://dev.clojure.org/jira/secure/IssueNavigator.jspa?reset=true&jqlQuery=labels+%3D+shell An XML representation of a search request en-us 4.4 649 25-07-2011 http://dev.clojure.org/jira/browse/CLJS-159 ClojureScript <p>Bash completion shows `bin/cljsc.bat` as an executable on UNIX systems<br/> making it very easy to accidentally execute it. However, since <br/> Windows command scripts do not work with UNIX shells, it is not <br/> advisable to allow executable permissions to Windows batch scripts <br/> as accidentally executing them may cause undefined behavior on such <br/> systems.</p> <p>I strongly suggest stripping UNIX shell executable permissions from<br/> `bin/cljsc.bat`.</p> <p>Thank you.</p> <p>Cheers,<br/> Yesudeep.</p> Any UNIX platform. CLJS-159

Suggest removing UNIX shell executable permissions from bin/cljsc.bat

Defect Major Resolved Completed Unassigned Yesudeep Mangalapilly command executable linux permissions script shell unix windows Tue, 6 Mar 2012 23:31:45 -0600 Wed, 14 Mar 2012 19:22:43 -0500 Wed, 14 Mar 2012 19:22:43 -0500 0 0 <p>The issue also affects:</p> <p> bin/cljsc.bat<br/> script/repljs.bat<br/> script/repl.bat</p> <p>I've verified (on both Ubuntu Linux and Windows 7) that stripping the x bit from those files has the desired effect.</p> <p>The patch is almost too trivial to bother with listing here, but here it is regardless: </p> <div class="preformatted panel" style="border-width: 1px;"><div class="preformattedContent panelContent"> <pre>diff --git a/bin/cljsc.bat b/bin/cljsc.bat old mode 100755 new mode 100644 diff --git a/script/repl.bat b/script/repl.bat old mode 100755 new mode 100644 diff --git a/script/repljs.bat b/script/repljs.bat old mode 100755 new mode 100644 </pre> </div></div> <p>Fixed, <a href="https://github.com/clojure/clojurescript/commit/aa51a01141131736871e791918df63f185155421">https://github.com/clojure/clojurescript/commit/aa51a01141131736871e791918df63f185155421</a></p> Global Rank http://dev.clojure.org/jira/browse/CLJ-959 Clojure <p>Create the following four-line file, shell_example.clj:</p> <p>;; simple example of call to sh that causes jvm to hang after print<br/> (require '<span class="error">&#91;clojure.java.shell :as shell&#93;</span>)<br/> (shell/sh "ls")<br/> (println "jvm should exit after this, but it doesn't")</p> <p>Run:<br/> java -jar clojure-1.3.0.jar shell_example.clj</p> <p>After the message is printed, the jvm doesn't quit. It just sits there. I have to hit Ctrl-C to force the jvm to quit.</p> <p>This happens on 1.3 and the most recent code in github as of 3/26/2012. I imagine the jvm is waiting for a thread that hasn't terminated, but the code in the sh function doesn't look like it's doing anything obviously wrong. I'm too much of a newcomer to Clojure to dig any deeper.</p> <p>My workaround right now is to do (System/exit 0) to force the jvm to quit.</p> <p>Thank you for your work on Clojure, it's simply an amazing language.</p> Reproduced on Ubuntu using Sun Java 1.6, OpenJDK 1.6, and Sun Java 1.7 <br/> CLJ-959

after call to clojure.java.shell/sh, jvm won't exit

Defect Major Open Unresolved Unassigned Jeff Chiu shell Mon, 26 Mar 2012 21:55:26 -0500 Fri, 8 Jun 2012 12:47:07 -0500 Release 1.3 Release 1.4 0 1 <p>Jeff, this occurs in any Clojure program where certain threading mechanisms are invoked. In your case, clojure.java.shell/sh uses future, which causes threads to be created that then sit around for about 60 seconds after everything else quits, and the main Java process does not exit until that happens. Another way to get the program to exit quickly is to call (shutdown-agents), but that isn't any more convenient than (System/exit 0), nor is there any obvious way you can tell as a newcomer that you should be doing this.</p> <p>The ticket <a href="http://dev.clojure.org/jira/browse/CLJ-124" title="GC Issue 120: Determine mechanism for controlling automatic shutdown of Agents, with a default policy and mechanism for changing that policy as needed">CLJ-124</a> is marked with status "Approved" at this time, which leads me to believe that perhaps soon there will be a change made to Clojure such that this situation will change.</p> <p>This behavior is now documented on clojuredocs.org for future, and both pmap and clojure.java.shell/sh refer to future for details.</p> Global Rank