Viktor Rosenfeld wrote:
> ...
> One more question, it doesn't matter if I put the code in the
> file that is loaded via -l or in the --eval block, correct? I've
> included the code in the my org file, so I can tangle it. I find it
> better to have all the Emacs code in one location.
>
Correct.
Hi Nick,
Nick Dokos wrote:
> The usual method is to run a separate emacs in batch mode: that will avoid
> any conflicts
> with the running instance. But batch implies -q, so you will have to provide
> a minimal .emacs
> file that sets up enough structure to enable you to do what you want:
>
>
Viktor Rosenfeld wrote:
> Hi,
>
> Jambunathan K wrote:
>
> >
> > C-h v org-export-run-in-background
>
> This only works for org-export, but not for org-export-as-XXX.
>
> Additionally, it appears that setting org-confirm-babel-evaluate locally
> does not have an effect on background exports.
Hi,
Jambunathan K wrote:
>
> C-h v org-export-run-in-background
This only works for org-export, but not for org-export-as-XXX.
Additionally, it appears that setting org-confirm-babel-evaluate locally
does not have an effect on background exports. Even setting it globally
in a running Emacs ins
C-h v org-export-run-in-background
> Hi,
>
> is it possible to export an org file from the command line, so that a
> currently running Emacs instance is not disturbed? I want to export the
> attached org file and run the included source blocks, so I have an
> activity report in the end. I use the
Hi,
is it possible to export an org file from the command line, so that a
currently running Emacs instance is not disturbed? I want to export the
attached org file and run the included source blocks, so I have an
activity report in the end. I use the shell script pasted below, but
there are two pr
