Re: questionable result of Clojure code execution in org babel

2019-09-08 Thread Johannes
Am Mittwoch, 4. September 2019 13:19:30 UTC+2 schrieb Johannes: > > Until today there is no response to my post on org mode list. > > In the meantime I've upgraded Aquamacs to the lastest stable version (3.5) > and upgraded all my packages (esp. Org mode version 9.2.6). > If I now try to execute

Re: questionable result of Clojure code execution in org babel

2019-09-04 Thread Johannes
Until today there is no response to my post on org mode list. In the meantime I've upgraded Aquamacs to the lastest stable version (3.5) and upgraded all my packages (esp. Org mode version 9.2.6). If I now try to execute the the following code section in an org-mode file with C-c C-c #+BEGIN_SR

Re: questionable result of Clojure code execution in org babel

2019-08-13 Thread numbch...@gmail.com
Sorry about this, I forgot most of I did in this patch. Actually I modified it some times in different version. I can find out the discussion mail thread. Here it is: https://lists.gnu.org/archive/cgi-bin/namazu.cgi?query=%3Ans&submit=Search%21&idxname=emacs-orgmode&max=20&result=normal&sort=score

Re: questionable result of Clojure code execution in org babel

2019-08-12 Thread Peter Hull
On Monday, 12 August 2019 18:47:48 UTC+1, Alex Miller wrote: > > You can’t wrap ns and forms into a single do like that. If you google > around you can find this issue referred to as the Gilardi scenario. OK, thanks, Alex. Is this not covered in https://technomancy.us/143 by the para that starts

Re: questionable result of Clojure code execution in org babel

2019-08-12 Thread Alex Miller
You can’t wrap ns and forms into a single do like that. If you google around you can find this issue referred to as the Gilardi scenario. -- 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 No

Re: questionable result of Clojure code execution in org babel

2019-08-12 Thread Peter Hull
On Friday, 9 August 2019 11:52:32 UTC+1, Johannes wrote: > > I posted the problem there. > Not a great response so far, I see! I had another little play and it may be possible to solve by a small change to ob-clojure.el. Basically we just wrap the forms and the ns into a single (do ...) form.

Re: questionable result of Clojure code execution in org babel

2019-08-09 Thread Johannes
Am Freitag, 9. August 2019 08:36:32 UTC+2 schrieb numb...@gmail.com: > > Actually I commited that patch, I intened to fix a problem in ob-clojure > which also is a feature for ob-clojure allow user can specify `:ns` header > argument. I noticed this result problem. I tried to dig in. But have n

Re: questionable result of Clojure code execution in org babel

2019-08-08 Thread numbch...@gmail.com
Actually I commited that patch, I intened to fix a problem in ob-clojure which also is a feature for ob-clojure allow user can specify `:ns` header argument. I noticed this result problem. I tried to dig in. But have no lucky. Maybe someone in Org Mode mailing list can help. [stardiviner]

Re: questionable result of Clojure code execution in org babel

2019-08-08 Thread Peter Hull
On Thursday, 8 August 2019 17:00:43 UTC+1, Johannes wrote: > > Thank you, Pete, for your investigation. > OK, I would be interested to hear if you get this sorted out! -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to this group, send emai

Re: questionable result of Clojure code execution in org babel

2019-08-08 Thread Johannes
Thank you, Pete, for your investigation. Am Mittwoch, 7. August 2019 14:37:06 UTC+2 schrieb Peter Hull: > > On Wednesday, 7 August 2019 12:42:07 UTC+1, Peter Hull wrote: > > > The connection returns two values, first 'nil' then '24', and function > nrepl--merge concats these into the incorrect r

Re: questionable result of Clojure code execution in org babel

2019-08-07 Thread Peter Hull
On Wednesday, 7 August 2019 12:42:07 UTC+1, Peter Hull wrote: The connection returns two values, first 'nil' then '24', and function nrepl--merge concats these into the incorrect response that org-mode pastes into your doc. Wait, might be on to something here. In org-mode 9.1.9 the sent messag

Re: questionable result of Clojure code execution in org babel

2019-08-07 Thread Peter Hull
I poked around at this a bit. If you enable nrepl's logging (use nrepl-toggle-message-logging) you will see something like this: (--> id "18" op "eval" session"86281560-e467-47c4-869d-043b03f5c546" time-stamp "2019-08-07 12:23:33.769213028" code "(ns org-babel-c

Re: questionable result of Clojure code execution in org babel

2019-08-06 Thread Johannes
My versions: ;; org-mode 9.2.5 ;; Aquamacs 3.5 GNU Emacs 25.3.50.1 ;; CIDER 0.21.0 (New York), nREPL 0.6.0 ;; Clojure 1.9.0, Java 11 Is there a better place to post the problem? Johannes -- You received this message because you are subscribed to the Google Groups "Clojure" group. To post to t

Re: questionable result of Clojure code execution in org babel

2019-08-06 Thread Peter Hull
On Monday, 5 August 2019 17:12:41 UTC+1, Johannes wrote: > > What is going wrong? > I tried Emacs 'built-in' org mode (9.1.9) and it gave the correct result, I then installed 9.2.5 and that did give the incorrect result that you reported. So, I assume something changed in org-mode between 9.1.9 a