From mboxrd@z Thu Jan 1 00:00:00 1970 From: Soapy Smith Subject: Re: Namespace problem org-mode / Clojure Date: Sun, 23 Feb 2014 10:41:00 -0500 Message-ID: <1393170060.2128.14.camel@raven-CM5571> References: Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:39862) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHbBE-0002s9-4Y for emacs-orgmode@gnu.org; Sun, 23 Feb 2014 10:41:33 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1WHbB4-0005Gg-KG for emacs-orgmode@gnu.org; Sun, 23 Feb 2014 10:41:23 -0500 Received: from qmta15.westchester.pa.mail.comcast.net ([2001:558:fe14:44:76:96:59:228]:36314) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1WHbB4-0005GX-CI for emacs-orgmode@gnu.org; Sun, 23 Feb 2014 10:41:14 -0500 In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Volker Strobel Cc: emacs-orgmode@gnu.org, "Thomas S. Dye" Hi Volker- I tried the your example code blocks on my system, and I concur with most of the behavior you described. org-babel-execute-buffer does not work, as it comes back with error "repl not connected". It did not cause a crash. However, if I add explicit namespace declaration to the 2nd block, it works! This is true even thought the 3rd block does not(???). I was thinking back to why I never encountered this problem, and it is because I have almost always used an explicit namespace declaration at the top of the block. Fortunately, after the first block, you don't have to use the optional parameters, includes etc. In your example (ns environment.my-test) added to subsequent code blocks you wish to execute in the same namespace should be sufficient. I think this should be considered the "work-around" until someone can explain what is going on, or, even better, can fix this. I'm the person who updated the worg documentation for Clojure code blocks. I'm thinking about adding a list of TODOs at the bottom, as there have been some other requests recently to the function behavior. This issue definitely will go on the list. Hopefully Bastien is monitoring and can comment if this is appropriate to add to the Clojure specific worg page (or should it go somewhere else). Regards, Greg