[O] Table (used a "spreadsheet") org-sbe issues when the value is a string

Hi Everybody, I am experiencing a few issues trying to update a cell value using =org-sbe= when the value of a column is a string. Here is an example that works when the value is a number: #+NAME: average-dataset-size #+BEGIN_SRC clojure :var f="turtle" :exports none

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi Jon, You can see a commented out version for shell blocks here: https://github.com/jkitchin/jmax/blob/master/jmax-org.el#L936 It looks like I just redefined the org-babel-execute:sh function after it was loaded. That may not be recommended good practice, but it works ;) I am not sure why

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi John, Here is a blog post that explains the changes I did. I still have one improvement to do (but don't how it could be done or even if it can be done) which is explained at the end of the post:

[O] Does org-babel-tangle-jump-to-code exists?

Hi Everybody, I was wondering if something like "org-babel-tangle-jump-to-code" exists anywhere? I am looking for a way to jump to a tangled file from the Org file, and not the opposite (which is handled using "org-babel-tangle-jump-to-org"). Thanks, Fred

Re: [O] [PATCH] expose nrepl's timeout setting in ob-clojure.el

Hi Nicolas, Some keywords are missing: :version "25.1" :package-version '(Org . "9.0") and perhaps :safe #'wholenump Ok good, added. (defcustom org-babel-clojure-backend (cond ((featurep 'cider) 'cider) (t 'slime)) @@ -94,8 +100,9 @@ (let ((result-params

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi, Yes, you are. There is a "go to the topic" action on the left panel. Anyway, there is not much to see, just some pointers to start a discussion. Haa great thanks, see it now :) Let me revise a few things, suggest another patch, and then will start to think about these things. Thanks,

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi Nicolas, Here is a blog post that explains the changes I did. I still have one improvement to do (but don't how it could be done or even if it can be done) which is explained at the end of the post:

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi Nicolas, However, I am not sure neither how generic such a solution could be, and what would still be required to implement in each OB plugin. My (very little) experience so far is the Python prototype that John wrote, and then my analysis of the Clojure OB plugin. As I was explaining in

Re: [O] [PATCH] expose nrepl's timeout setting in ob-clojure.el

he change... Patch attached. Hope everything is good now! Thanks, Fred >From c8e89d774590e9b39604252b3a344f95b56e3924 Mon Sep 17 00:00:00 2001 From: Frederick Giasson <f...@fgiasson.com> Date: Wed, 6 Apr 2016 10:00:18 -0400 Subject: [PATCH] Document the new option ob-clojure option

[O] [PATCH] new :async feature for org-babel-clojure

:00 2001 From: Frederick Giasson <f...@fgiasson.com> Date: Wed, 6 Apr 2016 12:18:21 -0400 Subject: [PATCH 3/4] Adding information about the new org-babel-clojure :async feature. --- etc/ORG-NEWS | 9 + 1 file changed, 9 insertions(+) diff --git a/etc/ORG-NEWS b/etc/ORG-NEWS inde

[O] [PATCH] expose nrepl's timeout setting in ob-clojure.el

Hi everybody, I am starting to use org-mode to create literate applications in Clojure. So far so good, this is a terrific piece of software. One thing why I wanted to use org-mode is to use it to create Clojure Notebooks. The problem I had is that I have many functions that can take some

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi Eric, Note: I am not sure if this is something related to Org-mode, or ob-clojure or Cider. None of these directly. It's Emacs, basically: it has very minimal support for threading so the whole process (Emacs) is waiting for the sub-process (Clojure) to finish before doing anything else.

[O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi everybody, I was wondering if it was possible for Org-mode to write results in #+RESULTS as soon as something is written to STDOUT? Here is my issue: I am writing Notebooks in Clojure using org-mode (clojure). I have some long-running procedures in the notebook that output the current

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

last bit of the post. http://kitchingroup.cheme.cmu.edu/blog/2015/11/20/Asynchronously-running-python-blocks-in-org-mode/ Maybe you could adapt it for clojure. Frederick Giasson writes: Hi Eric, Note: I am not sure if this is something related to Org-mode, or ob-clojure or Cider. None of t

Re: [O] ob-clojure: possible to display results as soon as something is written to STDOUT?

Hi John, you should rename it org-babel-async-execute:clojure, and adapt it to run clojure. Yes I wrote the function in the org-file that is that post, and executed the code block (C-c C-c) which "registers" the function for that instance of emacs. I am not sure I understand here. Once

Re: [O] [PATCH] new :async feature for org-babel-clojure

Hi Nicolas, Right now, async is really more about "feedback" than "asynchronous". However it has never been clear is it was possible or not, and if so, how :) Any pointers on how this could be done in emacs? You could start a new Emacs evaluating some code in a subprocess, with

Re: [O] [PATCH] new :async feature for org-babel-clojure

Hi Nicolas, Any news regarding these latest fixes to that patch? Thanks, Fred Here is my proposal to create a new :async feature for Org-babel-clojure. This is discussed at length in this blog post:

Re: [O] [PATCH] new :async feature for org-babel-clojure

Hi Nicolas, As for 3 and 4, I think a more general mechanism for asynchrnous eval'ing would be preferable. Besides, AFAIU, because of ; Wait until the nREPL code finished to be processed (while (not (member "done" status)) (nrepl-dict-put response "status" (remove "need-input"

[O] Org-list-todo not accessible via "C-c a t"?

Hi, I am using the latest code, and I am wondering where did the org-list-todo keybinding goes? Given the documentation, I should be able to get is via "C-c a t", but the "t" is not available in the options. But the latest Worg still have "C-c a t" as the binding. Am I missing something?

Re: [O] ob-clojure?

Hi Lawrence, Is there an ob-clojure in elpa? If not should I use this ? You may be interested in this version: http://fgiasson.com/blog/index.php/2016/06/16/improving-org-babel-clojure/ I didn't find the time to push

[O] Bug: HTML exports issues: none not working, and issues with #+TITLE

Hi, I upgraded to Emacs 25.1 and Org-mode 9.0 (latest from Elpa) and I am experiencing two issues with export: (1) The header parameter ":exports none" doesn't appear to be working. With the following code, the code block is exported to HTML: = #+BEGIN_SRC elisp :results

Re: [O] Bug: HTML exports issues: none not working, and issues with #+TITLE

Hi Nicolas, Thanks anyway, this answer led me to do some more research. What did work for me is this: http://emacs.stackexchange.com/a/16616/13925 Only running C-u M-x org-reload was fixing the issue, but when I restarted Emacs, it was restarting. Doing org-reload, uninstall and

Re: [O] Bug: HTML exports issues: none not working, and issues with #+TITLE

Hi Nicolas, This seem to indicate you have a mixed installation. See, e.g., . I am getting a 404 error for that page, would you have another link for that thread? Thanks, Fred

[O] HTML export with ":export" parameter with Orgmode 9.0

Hi, I am not clear about the change in the Export blocks that occurred in Org-mode 9.0 Does this change impact the ":export [...]" code block header parameter? What I am often using is this: http://orgmode.org/manual/Exporting-code-blocks.html Which currently doesn't work but it

Re: [O] [BUG] org-create-formula-image requires 'gs' when it doesn't look like to be necessary (causing issues on Windows)

Hi Nicolas, Do you mean that "gs" could be removed from all entries in `org-preview-latex-process-alist'? I'm Cc'ing Feng Shu, who implemented the new LaTeX preview mechanism. He hopefully knows why this dependency was introduced in the first place. I think so yes, at least on Windows

Re: [O] [BUG] org-create-formula-image requires 'gs' when it doesn't look like to be necessary (causing issues on Windows)

Hi again, There is one thing I forgot to mention: PDF/LateX export was working fine. Thanks, Fred Hi, I am a Windows user and I am testing the Org 9.x branch. I just discovered that I couldn't display inline latex anymore using C-c C-x C-l. I was getting that error:

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

Hi Nicolas, It seems other users experienced it, yet it is unexpected and I cannot reproduce it even with a minimal init file. Ok good. I will try to do some debugging on my side. I am wondering if it may not be a Windows issue, or some older 8.x configurations that may be at cause here.

[O] [BUG] org-create-formula-image requires 'gs' when it doesn't look like to be necessary (causing issues on Windows)

Hi, I am a Windows user and I am testing the Org 9.x branch. I just discovered that I couldn't display inline latex anymore using C-c C-x C-l. I was getting that error: org-create-formula-image: Can’t find ‘gs’ (you need to install the programs: latex, dvipng and ghostscript.) A

Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

Hi Nicolas, I noticed that you included some of my previous fixes in Org-babel-clojure, so here are the latest work I did. I updated it to work with the latest code on Git. I did two things with these fixes: (1) I better handle any possible error or exceptions that may be raised by nREPL

[O] [PATCH] New header parameter :show-process for Org-babel-clojure

nks! Take care, Fred From df8284b45c35e0c1dcbccf40ba7b76fd18270b90 Mon Sep 17 00:00:00 2001 From: Frederick Giasson <f...@fgiasson.com> Date: Mon, 7 Nov 2016 13:48:50 -0500 Subject: [PATCH 1/2] Better error handling with nREPL. Displaying any possible errors or exceptions in the result block. Addin

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

Hi Charles, Setting `org-export-babel-evaluate' to nil will ensure that NONE of your header arguments are followed. Like the docstring says "Users who wish to avoid evaluating code on export should use the header argument ‘:eval never-export’." It is tempting to `make-obsolete-variable'

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

Hi Chuck, even with a minimal init file. If you ever set the value of `org-export-babel-evaluate' to nil this might produce the behavior you describe. Maybe, but as stated in the manual: "Setting the org-export-babel-evaluate variable to nil will ensure that no code blocks are evaluated

Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

, Fred >From 3eb282c554f8099627b748e7c4eb07d0e810a2ae Mon Sep 17 00:00:00 2001 From: Frederick Giasson <f...@fgiasson.com> Date: Mon, 14 Nov 2016 15:43:16 -0500 Subject: [PATCH] Multiple improvements of ob-clojure have been performed in this commit. (1) better error handlin

Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

Hi Nicolas, Great! Please let me know once the process is complete, so that I can apply your patch in master. I am still waiting for FSF's signature. Should come in soon I guess. Thanks, Fred

Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

Hi, It looks like this warning results from a defcustom for this variable not being included in the patch (and AFAICT it should be). Humm, I thought that it was already part of Org-mode 8.x (something I submitted a way back). Let me check that. If I have to add it again, should I recreate

Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

to that. Thanks, Fred >From e68c5611f00eb37783205352d68efb7feccae8ab Mon Sep 17 00:00:00 2001 From: Frederick Giasson <f...@fgiasson.com> Date: Fri, 18 Nov 2016 10:29:16 -0500 Subject: [PATCH] Adding the defcustom for the "org-babel-clojure-sync-nrepl-timeout" variable used to

Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

Hi Nicolas, In end of data: ob-clojure.el:180:1:Warning: the following functions are not known to be defined: nrepl-request:eval, nrepl--merge, nrepl-dict-put Could you look into it? In particular, "nrepl--merge" looks like an internal function from nrepl. Is it safe to use it?

Re: [O] [PATCH] New header parameter :show-process for Org-babel-clojure

Hi Nicolas, Could you recreate the commit so it is self-contained? That should be it. Thanks, Fred >From e19c358f9d4cab9b22c3e4e3bf6b8f6298e61b0e Mon Sep 17 00:00:00 2001 From: Frederick Giasson <f...@fgiasson.com> Date: Fri, 18 Nov 2016 12:01:02 -0500 Subject: [PATCH]

Re: [O] HTML export with ":export" parameter with Orgmode 9.0

Hi Nicolas, It seems other users experienced it, yet it is unexpected and I cannot reproduce it even with a minimal init file. Ok I think I found the issue. In all the files I worked on since I upgraded to 9.0 I had the following setting at the top of my org files: = # -*-

Re: [O] org-detangle seems broken

Hi Grant, I think it is expected. The code looks like this: > > (when (setq new-body (org-babel-tangle-jump-to-org)) > (org-babel-update-block-body new-body)) > Yeah not sure I fully understand that code. Basically it does this for each code block that needs to be detangled right? I am

[O] Issues with org-babel-detangle and :comments noweb

Hi Everybody, I am trying to have noweb references working with org-babel-detangle. Let's use this example: ``` #+NAME: a #+BEGIN_SRC clojure (def a "a") #+END_SRC #+NAME: b #+BEGIN_SRC clojure (def a "b") #+END_SRC #+NAME: c #+BEGIN_SRC clojure (def a "c") #+END_SRC #+NAME: a

Re: [O] org-detangle seems broken

ng the ECM is if there is only *one* code block in the =.org= file, then it throws a =End of Buffer= error. On Sat, Jun 2, 2018 at 6:17 AM, Nicolas Goaziou wrote: > Hello, > > Frederick Giasson writes: > > > It appears that org-detangle is broken. I am using spacemacs, but eve

Re: [O] org-detangle seems broken

Hi Nicolas, > Here it is. If you =detangle= the =broken-detangle--working.el= file, it > > will work as expected. > > > > However, if you try to detangle the =broken-detangle--NOT-working.el= > file, > > you should get a "Not in a source block" error in *message*. > > This is fixed in "master". >

Re: [O] org-detangle seems broken

Hi > > > block to its tangled source is created, then we could use it with that > option in `org-babel-detangle` to switch back to the source if it is the > wish of the user. > > It sounds like org-babel-tangle-jump-to-org is what you want. > In fact it is its opposite that I need, code block

[O] org-detangle seems broken

Hi Everybody, It appears that org-detangle is broken. I am using spacemacs, but even with a vanilla Emacs (emacs -Q) it appears to be broken. When I tangle a file with =:comments link= every things works as expected and the comments are added in the tangled file. When I just detangle that

[O] ob-clojure with tangling current broken

Hi, I updated org-mode to latest dev version recently and I was wondering why I was seeing namespaces appended to each [clojure] code block I was tangling (which generates unusable tangled Clojure source files) It turns out that the culprit is the following line:

Re: [O] ob-clojure with tangling current broken

Hi, That's why I added a patch recently. Now Nicolas already applied my > patch. You should already seen it now. > Yeah I just received that email right after I sent mine. Didn't know it was in the pipeline, I just re-subscribed to the mailing list. > > > > It turns out that the culprit is the