Re: [O] version 7.9.3d: compilation fails -- solved, thanks!
> Please edit local.mk to have make use the correct Emacs at least. Just to confirm that setting the EMACS variable solved the problem, thanks. I also want to confirm that org-compat.el and org-odt.el now load again, without any hacks necessary anymore in ~/.emacs. Thanks again! Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
Re: [O] version 7.9.3d: compilation fails
> I just had some trouble with a certain git version. $ git --version git version 1.7.10.3 Thanks again! Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
Re: [O] version 7.9.3d: compilation fails
When starting emacs with the unsuccessfully compiled latest version Emacs says Warning (initialization): An error occurred while loading `/Users/torsten/.emacs': Symbol's value as variable is void: org-babel-temp-file > It might be unrelated, but does 'M-x load-library RET org.el' work with your > latest version? Same problem: Loading /Users/torsten/emacs/org-mode/lisp/org.el (source)... require: Symbol's value as variable is void: org-babel-temp-file Note that this very error was reported many times during the compilation process. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
[O] version 7.9.3d: compilation fails
Dear all, I tried to update orgmode to the latest version 7.9.3d, but make failed, see outputs after this email. I am on MacOS 10.6.8, and I do not know which emacs the unedited make file uses, quite possibly the preinstalled Emacs at the shell. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de - Infoserves-MacBook-Pro-69:org-mode torsten$ make == = Invoke "make help" for a synopsis of make targets. = = Created a default local.mk template. = = Setting "oldorg" as the default target.= = Please adapt local.mk to your local setup! = == Loading /Users/torsten/emacs/org-mode/lisp/org-compat.el (source)... Loading /Users/torsten/emacs/org-mode/mk/org-fixup.el (source)... Wrote /Users/torsten/emacs/org-mode/local.mk make -C doc clean; make -C lisp clean; rm -f org *.pdf *.html *_letter.tex org-version.inc \ *.aux *.cp *.cps *.dvi *.fn *.fns *.ky *.kys *.pg *.pgs \ *.toc *.tp *.tps *.vr *.vrs *.log *.html *.ps rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc rm -f *.elc make -C lisp compile rm -f org-version.el org-loaddefs.el org-version.elc org-loaddefs.elc org-install.elc org-version: 7.9.3d (7.9.3d-dist) Loading /Users/torsten/emacs/org-mode/lisp/org-compat.el (source)... Loading /Users/torsten/emacs/org-mode/mk/org-fixup.el (source)... Wrote /Users/torsten/emacs/org-mode/lisp/org-version.el org-loaddefs: 7.9.3d (7.9.3d-dist) Loading /Users/torsten/emacs/org-mode/lisp/org-compat.el (source)... Loading /Users/torsten/emacs/org-mode/mk/org-fixup.el (source)... Generating autoloads for ob-C.el... Generating autoloads for ob-C.el...done Generating autoloads for ob-R.el... Generating autoloads for ob-R.el...done Generating autoloads for ob-asymptote.el... Generating autoloads for ob-asymptote.el...done Generating autoloads for ob-awk.el... Generating autoloads for ob-awk.el...done Generating autoloads for ob-calc.el... Generating autoloads for ob-calc.el...done Generating autoloads for ob-clojure.el... Generating autoloads for ob-clojure.el...done Generating autoloads for ob-comint.el... Generating autoloads for ob-comint.el...done Generating autoloads for ob-css.el... Generating autoloads for ob-css.el...done Generating autoloads for ob-ditaa.el... Generating autoloads for ob-ditaa.el...done Generating autoloads for ob-dot.el... Generating autoloads for ob-dot.el...done Generating autoloads for ob-emacs-lisp.el... Generating autoloads for ob-emacs-lisp.el...done Generating autoloads for ob-eval.el... Generating autoloads for ob-eval.el...done Generating autoloads for ob-exp.el... Generating autoloads for ob-exp.el...done Generating autoloads for ob-fortran.el... Generating autoloads for ob-fortran.el...done Generating autoloads for ob-gnuplot.el... Generating autoloads for ob-gnuplot.el...done Generating autoloads for ob-haskell.el... Generating autoloads for ob-haskell.el...done Generating autoloads for ob-io.el... Generating autoloads for ob-io.el...done Generating autoloads for ob-java.el... Generating autoloads for ob-java.el...done Generating autoloads for ob-js.el... Generating autoloads for ob-js.el...done Generating autoloads for ob-keys.el... Generating autoloads for ob-keys.el...done Generating autoloads for ob-latex.el... Generating autoloads for ob-latex.el...done Generating autoloads for ob-ledger.el... Generating autoloads for ob-ledger.el...done Generating autoloads for ob-lilypond.el... Generating autoloads for ob-lilypond.el...done Generating autoloads for ob-lisp.el... Generating autoloads for ob-lisp.el...done Generating autoloads for ob-lob.el... Generating autoloads for ob-lob.el...done Generating autoloads for ob-matlab.el... Generating autoloads for ob-matlab.el...done Generating autoloads for ob-maxima.el... Generating autoloads for ob-maxima.el...done Generating autoloads for ob-mscgen.el... Generating autoloads for ob-mscgen.el...done Generating autoloads for ob-ocaml.el... Generating autoloads for ob-ocaml.el...done Generating autoloads for ob-octave.el... Generating autoloads for ob-octave.el...done Generating autoloads for ob-org.el... Generating autoloads for ob-org.el...done Generating autoloads for ob-perl.el... Generating autoloads for ob-perl.el...done Generating autoloads for ob-picolisp.el... Generating autoloads for ob-picolisp.el...done Generating autoloads for ob-plantuml.el... Generating autoloads for ob-plantuml.el...done Generating autoloads for ob-python.el... Generating autoloads for ob-python.el...done Generating autoloads for ob-ref.el... Generating autoloads for ob-ref.el...done Generating autoloads for ob-ruby.el... Generating autoloads for ob-ruby.el...done Generating autoloads for ob-sass.el... Generating autoloads f
Re: [O] Opendocument export causes error
> > When the err happens, > > 1. Load Emacs like this. Adjust the `-L's. Note also the -Q. > > emacs --debug-init -L ~/src/org-mode/lisp -L > ~/src/org-mode/contrib/lisp -Q > > 2. M-x load-library RET org-odt RET > > 3. M-x ielm RET > > Here is a sample session both for org-odt and org-e-odt. Sample > illustrates the sequence of events that led org-compat.el to be > loaded. > > The sequence below is courtesy this suggestion/thread: > http://lists.gnu.org/archive/html/help-gnu-emacs/2012-11/msg00227.html > > > So the load chain is: >org-compat <= org <= org-exp <= org-lparse <= org-odt > > , > | *** Welcome to IELM *** Type (describe-mode) for help. > | ELISP> (symbol-file 'org-compat 'require) > | "/home/kjambunathan/src/org-mode/lisp/org.elc" > | ELISP> (symbol-file 'org 'require) > | "/home/kjambunathan/src/org-mode/lisp/org-exp.elc" > | ELISP> (symbol-file 'org-exp 'require) > | "/home/kjambunathan/src/org-mode/lisp/org-lparse.elc" > | ELISP> (symbol-file 'org-lparse 'require) > | "/home/kjambunathan/src/org-mode/lisp/org-odt.elc" > | ELISP> (symbol-file 'org-odt 'require) > | nil > ` > > So the load chain is: >org-compat <= org <= org-element <= org-export <= org-e-odt > > , > | *** Welcome to IELM *** Type (describe-mode) for help. > | ELISP> (symbol-file 'org-compat 'require) > | "/home/kjambunathan/src/org-mode/lisp/org.elc" > | ELISP> (symbol-file 'org 'require) > | "/home/kjambunathan/src/org-mode/lisp/org-element.elc" > | ELISP> (symbol-file 'org-element 'require) > | "/home/kjambunathan/src/org-mode/contrib/lisp/org-export.el" > | ELISP> (symbol-file 'org-export 'require) > | "/home/kjambunathan/src/org-mode/contrib/lisp/org-e-odt.elc" > | ELISP> (symbol-file 'org-e-odt 'require) > | nil > | ELISP> (symbol-file 'org-macs 'require) > | "/home/kjambunathan/src/org-mode/lisp/org.elc" > ` > > ps: I hope I am invoking `symbol-file' properly. > > -- -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
Re: [O] Opendocument export causes error
r setup, > without their co-operation. > > Here is another suggestion. A bit easy one though. This will be > archived and will serve as a written hint to debug macro/autoload > issues. > > When the err happens, > > 1. Load Emacs like this. Adjust the `-L's. Note also the -Q. > > emacs --debug-init -L ~/src/org-mode/lisp -L > ~/src/org-mode/contrib/lisp -Q > > 2. M-x load-library RET org-odt RET > > 3. M-x ielm RET > > Here is a sample session both for org-odt and org-e-odt. Sample > illustrates the sequence of events that led org-compat.el to be > loaded. > > The sequence below is courtesy this suggestion/thread: >http://lists.gnu.org/archive/html/help-gnu-emacs/2012-11/msg00227.html > > > So the load chain is: > org-compat <= org <= org-exp <= org-lparse <= org-odt > >, >| *** Welcome to IELM *** Type (describe-mode) for help. >| ELISP> (symbol-file 'org-compat 'require) >| "/home/kjambunathan/src/org-mode/lisp/org.elc" >| ELISP> (symbol-file 'org 'require) >| "/home/kjambunathan/src/org-mode/lisp/org-exp.elc" >| ELISP> (symbol-file 'org-exp 'require) >| "/home/kjambunathan/src/org-mode/lisp/org-lparse.elc" >| ELISP> (symbol-file 'org-lparse 'require) >| "/home/kjambunathan/src/org-mode/lisp/org-odt.elc" >| ELISP> (symbol-file 'org-odt 'require) >| nil >` > > So the load chain is: > org-compat <= org <= org-element <= org-export <= org-e-odt > >, >| *** Welcome to IELM *** Type (describe-mode) for help. >| ELISP> (symbol-file 'org-compat 'require) >| "/home/kjambunathan/src/org-mode/lisp/org.elc" >| ELISP> (symbol-file 'org 'require) >| "/home/kjambunathan/src/org-mode/lisp/org-element.elc" >| ELISP> (symbol-file 'org-element 'require) >| "/home/kjambunathan/src/org-mode/contrib/lisp/org-export.el" >| ELISP> (symbol-file 'org-export 'require) >| "/home/kjambunathan/src/org-mode/contrib/lisp/org-e-odt.elc" >| ELISP> (symbol-file 'org-e-odt 'require) >| nil >| ELISP> (symbol-file 'org-macs 'require) >| "/home/kjambunathan/src/org-mode/lisp/org.elc" >` > > ps: I hope I am invoking `symbol-file' properly. > > -- -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
Re: [O] Opendocument export causes error
Dear Jambunathan, Again, thanks a lot for all your feedback. On 3 Dec 2012, at 06:01, Jambunathan K wrote: > Torsten Anders writes: >> One is the standard Emacs (in my case Aquamacs based on GNU Emacs >> 23.3.50.1) > > 50 in your Emacs version is an indication that it is a pre-pretest > version of Emacs. It seems you are OK with runnning a > non-released/unstable Emacs. This is the latest version of Aquamacs (http://aquamacs.org/), version 2.4. On a Mac, Aquamacs is by far the most convenient Emacs implementation I know of, if only for the antialiased font support and how easily font sizes are changed. The development version of Aquamacs uses Emacs 24, but I would like to avoid using that Aquamacs version before it is stable. Anyway, I assume I am not the only Aquamacs user on this list :) So, if the reported problem is due to Aquamacs then quite likely I am not the only one with this problem. I will go through your detailed list of suggestions a bit later. Thanks a lot again for your help! Best wishes, Torsten > I am not sure whether the port below is an Aquamacs. > > http://lists.gnu.org/archive/html/emacs-devel/2012-11/msg00472.html > > It is Emacs 24.2.90. One major version up and also a pre-test. You can > read the reaction of people in that thread. That version has a fairly > recent version of all org files. Notably an old org-compat that is > /very close/ to new org-compat. If the new port works, then you really > don't have to bother but just carry on with your work and bother less > about Org. > -- -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
Re: [O] Opendocument export causes error
Dear Achim, Thanks a lot for your help! > Try adding (require 'org) or alternatively — if you know you never > use the Org version that comes with Emacs (that means you need to be > extra careful with things like 'emacs -Q') — (require 'org-loaddefs). I tried both adding (require 'org) and (require 'org-loaddefs) to ~/.emacs but they both make no difference to this problem, I still get the error call-interactively: Symbol's value as variable is void: err Instead, adding the following to ~/.emacs does work, but this seems to be just a hack. Should I really use this? (load-library "org-compat.el") (load-library "org-odt.el") > here's your real-world example of how things don't work if the wrong autoload > definitions are used. Does this mean there are possibly more things that did not load as they should? Thanks a lot again! Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
[O] Opendocument export causes error
truction in this mail instead.) > > Symptoms tell me that you have a hoaxed installation. > > Try this and see if it helps > > M-x list-load-path-shadows RET > > Check where all org-odt.el is installed. Ideally you should see only > two paths - one from vanilla Emacs and one from directory that you are > trying to use right now. > > Try this next. > > M-x locate-library RET org-compat RET > M-x locate-library RET org-odt RET > > M-x locate-library RET org-compat.el RET > M-x locate-library RET org-odt.el RET > > (Note the presence of `.el' in later two commands) > > They should all come from the same directory tree. > > Try this next. > > M-x load-library RET org-compat.el RET > M-x load-library RET org-odt.el RET > > (Order of loading should be preserved. `.el' SHOULD be there) > > Now export. > > Look inside your messages buffer and examine what all ODT exporter is > trying to do. > > In all likelihood, you will have a successful export. > > For some more debugging, you can do, > > M-x locate-library RET org-install RET > M-x locate-library RET org-autoloads RET > M-x locate-library RET org-loaddefs RET > > (Try again the above commands with `.el' appended) > > Ideally your .emacs MUST have (require ') for only one of these > libraries. > > If you pass the censored logs from above commands then I or someone in > this list can guess what is possibly wrong. But my guess is above steps > should suffice to figure out the remedy. > >> Dear all, >> >> Since a while I cannot export to OpenDocument anymore. Instead, I >> always get the error >> >> call-interactively: Symbol's value as variable is void: err >> >> I just updated to Org-mode version 7.9.2 and the problem persists. In >> the archives I found exactly the same problem mentioned (messages from >> 11.07.2012 with subject Compile error in org-odt.el in latest master), >> but I do not understand the solution found then (Rainer Stengele >> reported that he "missed the unzip.exe and now it works"). >> >> Any help? Thanks! >> >> Best wishes, >> Torsten >> >> -- >> Dr Torsten Anders >> Course Leader, Music Technology >> University of Bedfordshire >> Park Square, Room A315 >> > http://www.torsten-anders.de > >> >> >> >> >>
[O] Opendocument export causes error
Dear all, Since a while I cannot export to OpenDocument anymore. Instead, I always get the error call-interactively: Symbol's value as variable is void: err I just updated to Org-mode version 7.9.2 and the problem persists. In the archives I found exactly the same problem mentioned (messages from 11.07.2012 with subject Compile error in org-odt.el in latest master), but I do not understand the solution found then (Rainer Stengele reported that he "missed the unzip.exe and now it works"). Any help? Thanks! Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de
[O] [PATCH] [Beamer export] Example should better export to exampleblock environment
Dear all, It is great that org mode makes creating Beamer slides so easy! I would like to include some green example blocks in my slides (e.g., for exercises for my students), and I can turn an org headline and its "content" into an example block by just pressing C-c C-b e -- very nice. Now, my problem is that Org mode exports this as a Beamer example environment, instead of an exampleblock environment. The difference is that the exampleblock environment is just a green block that otherwise behaves like the standard Beamer blocks (in particular, users have full control over its title), while an example environment always adds something to the title like this: Example (ACTUAL TITLE). Such behaviour may be useful in special cases, but the exampleblocks are more flexible and should therefore at least be supported as an alternative option, but likely being the default export option. Attached to this message there is a simple patch that adds support for exampleblocks (short cut C-c C-b E) by keeping everything else as it is. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://www.torsten-anders.de org-beamer.el.diff Description: Binary data
[O] [PATCH] Lilypond: added PDF output
Dear all, The current implementation how org-babel calls Lilypond hard-wires the supported output file formats to EPS and PNG. Attached is a very simple patch that adds support for PDF as well, so that resulting PDF files can be directly integrated in the PDF files generated by Latex and Latex Beamer support. Thanks! Best wishes, Torsten ob-lilypond.el.diff Description: Binary data
Re: [O] noweb problem
Ah, thanks a lot! I should develop the habit of reading the documentation of the development version when using that version... Best wishes, Torsten On 28 Nov 2011, at 20:14, Eric Schulte wrote: > Hi Torsten, > > The change here is in the naming conventions, "srcname" is no longer a > valid method of naming a code block, try "name" instead. e.g., > > #+name: sh-test-noweb > #+begin_src sh > ~ > #+end_src > > #+begin_src sh :noweb yes > ls <> > #+end_src > > Best, > > Torsten Anders writes: > >> Dear Org babel developers, >> >> In the simple test below I would expect that the second cope block >> expands to "ls ~", but seemingly it instead expands to "ls" only. What >> am I missing? >> >> #+srcname: sh-test-noweb >> #+begin_src sh >> ~ >> #+end_src >> >> #+begin_src sh :noweb yes >> ls <> >> #+end_src >> >> Did anything perhaps change in the literate programming interface? >> Apologies if I missed something obvious or if I am victim of some >> stupid typo. >> >> Thanks a lot! >> >> Best wishes, >> Torsten >> >> > > -- > Eric Schulte > http://cs.unm.edu/~eschulte/
[O] noweb problem
Dear Org babel developers, In the simple test below I would expect that the second cope block expands to "ls ~", but seemingly it instead expands to "ls" only. What am I missing? #+srcname: sh-test-noweb #+begin_src sh ~ #+end_src #+begin_src sh :noweb yes ls <> #+end_src Did anything perhaps change in the literate programming interface? Apologies if I missed something obvious or if I am victim of some stupid typo. Thanks a lot! Best wishes, Torsten
Re: [O] [org-babel] switching off (re-)evaluation of code blocks during Org export
Dear Eric, Sorry for the noise, it works fine. > see the manual for valid values for the eval header argument. I actually did, but only the online version so far. Of course, for such changes I had to check the doc sources... Anyway, thanks a lot!! Best wishes, Torsten On 28 Nov 2011, at 07:13, Eric Schulte wrote: > Hi Torsten, > > Change "non-export" to "no-export", see the manual for valid values for > the eval header argument. > > Best -- Eric > > Torsten Anders writes: > >> Dear Eric, >> >> Apologies for my late response (too much teaching and admin in this new job >> :-P). Thanks a lot again for kingly adding the "eval" header >> argument "non-export". From what I understand in your message this would be >> exactly what I was looking for (allow interactive >> evaluation, but inhibit code block evaluation during export). I just pulled >> the latest org sources and tested your addition. >> >> Unfortunately, even when using this header argument value, code blocks in >> both Lilypond and Fomus are still executed when the buffer is exported to >> either PDF (via Latex) or HTML. >> >> Below is a test that I understood should not execute during export. Am I >> missing something? >> >> >> #+begin_src fomus :eval non-export :results silent :file fomus-test.ly >> time 1 dur 1 pitch 60; >> #+end_src >> [[file:fomus-test.pdf]] >> >> Thanks a lot again! >> >> Best wishes, >> Torsten >> >> >> On 22 Nov 2011, at 01:23, Eric Schulte wrote: >> >>> Hi Torsten, >>> >>> Torsten Anders writes: >>> >>>> Dear Sebastien and Eric, >>>> >>>> Thanks a lot for your kind replies. However, this is not yet quite what I >>>> am after. >>>> >>>> I want to be able to manually execute each code block, but not >>>> automatically whenever the whole document is rendered. So, I would >>>> always switch on/off "eval never". Hm... >>>> >>> >>> I've just pushed up a patch which adds a new option to the "eval" header >>> argument. Setting eval to "non-export" will now allow interactive >>> evaluation, but will inhibit code block evaluation during export. This >>> should address your need as I understand it. >>> >>>> >>>> I will try out the ":cache" header argument. However, again this does >>>> not work so well, because for the languages I am using the :file >>>> argument does not work very well (I have to manually change >>>> extensions, so I include the resulting file links by hand anyway and >>>> set :results to silent. >>>> >>>> So, I it sounds like few org-babel users is really running larger >>>> applications in their code blocks which can delay the export of the >>>> whole document considerably. >>>> >>> >>> I would not jump to that conclusion. I have used babel code blocks to >>> cache the results of very long running results, however between the >>> :cache header argument and the ability to manually disassociate >>> generated results from code blocks I have not had any problems >>> inhibiting execution during export. >>> >>> Best -- Eric >>> >>>> >>>> Anyway, thanks a lot for your feedback. >>>> >>>> Best wishes, >>>> Torsten >>>> >>>> >>>> >>>> >>> >>> -- >>> Eric Schulte >>> http://cs.unm.edu/~eschulte/ >> > > -- > Eric Schulte > http://cs.unm.edu/~eschulte/
Re: [O] [org-babel] switching off (re-)evaluation of code blocks during Org export
Dear Eric, Apologies for my late response (too much teaching and admin in this new job :-P). Thanks a lot again for kingly adding the "eval" header argument "non-export". From what I understand in your message this would be exactly what I was looking for (allow interactive evaluation, but inhibit code block evaluation during export). I just pulled the latest org sources and tested your addition. Unfortunately, even when using this header argument value, code blocks in both Lilypond and Fomus are still executed when the buffer is exported to either PDF (via Latex) or HTML. Below is a test that I understood should not execute during export. Am I missing something? #+begin_src fomus :eval non-export :results silent :file fomus-test.ly time 1 dur 1 pitch 60; #+end_src [[file:fomus-test.pdf]] Thanks a lot again! Best wishes, Torsten On 22 Nov 2011, at 01:23, Eric Schulte wrote: > Hi Torsten, > > Torsten Anders writes: > >> Dear Sebastien and Eric, >> >> Thanks a lot for your kind replies. However, this is not yet quite what I am >> after. >> >> I want to be able to manually execute each code block, but not >> automatically whenever the whole document is rendered. So, I would >> always switch on/off "eval never". Hm... >> > > I've just pushed up a patch which adds a new option to the "eval" header > argument. Setting eval to "non-export" will now allow interactive > evaluation, but will inhibit code block evaluation during export. This > should address your need as I understand it. > >> >> I will try out the ":cache" header argument. However, again this does >> not work so well, because for the languages I am using the :file >> argument does not work very well (I have to manually change >> extensions, so I include the resulting file links by hand anyway and >> set :results to silent. >> >> So, I it sounds like few org-babel users is really running larger >> applications in their code blocks which can delay the export of the >> whole document considerably. >> > > I would not jump to that conclusion. I have used babel code blocks to > cache the results of very long running results, however between the > :cache header argument and the ability to manually disassociate > generated results from code blocks I have not had any problems > inhibiting execution during export. > > Best -- Eric > >> >> Anyway, thanks a lot for your feedback. >> >> Best wishes, >> Torsten >> >> >> >> > > -- > Eric Schulte > http://cs.unm.edu/~eschulte/
Re: [O] [org-babel] switching off (re-)evaluation of code blocks during Org export
Dear Sebastien and Eric, Thanks a lot for your kind replies. However, this is not yet quite what I am after. I want to be able to manually execute each code block, but not automatically whenever the whole document is rendered. So, I would always switch on/off "eval never". Hm... I will try out the ":cache" header argument. However, again this does not work so well, because for the languages I am using the :file argument does not work very well (I have to manually change extensions, so I include the resulting file links by hand anyway and set :results to silent. So, I it sounds like few org-babel users is really running larger applications in their code blocks which can delay the export of the whole document considerably. Anyway, thanks a lot for your feedback. Best wishes, Torsten
[O] [org-babel] switching off (re-)evaluation of code blocks during Org export
Dear Org-Babel developers, When I am exporting an *.org buffer to, say, HTML or PDF (via Latex) the code blocks of at least some languages are executed during the export process. (Has this always been like that, I noticed this for the first time?) I would like to switch that off completely. I prefer evaluating code blocks individually to check their results. Also, many of by code blocks run substantial programs which slow down the export process considerably. I could not find an option to switch this off in the documentation. Apologies if I missed something obvious. I assume it is there somewhere, but I could not find it. Thank you! Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 torsten.and...@beds.ac.uk http://strasheela.sourceforge.net http://www.torsten-anders.de
Re: [O] Bugs in lisp/ob-lilypond.el
Also, the setting results: silent seems to be ignored. Best wishes, Torsten On 19 Nov 2011, at 15:22, Torsten Anders wrote: > Dear Martyn Jago, dear all, > > I just pulled the latest version of Org mode and noticed a few bugs in the > Lilypond support of Org babel that have not been there in the previous > version (so far I was still using version 7.6). > > In general, there seems to be problems in parsing the line that starts > #+begin_src lilypond. More specifically, > > - Global :noweb settings are now ignored > - Any settings after the setting :file will be added to output file name! > - Settings after :noweb yes cause trouble (disable this setting) > > Again, thanks for lisp/ob-lilypond.el in the first place. > > Best wishes, > Torsten > > -- > Dr Torsten Anders > Course Leader, Music Technology > University of Bedfordshire > Park Square, Room A315 > torsten.and...@beds.ac.uk > http://strasheela.sourceforge.net > http://www.torsten-anders.de > > > > > > >
[O] Bugs in lisp/ob-lilypond.el
Dear Martyn Jago, dear all, I just pulled the latest version of Org mode and noticed a few bugs in the Lilypond support of Org babel that have not been there in the previous version (so far I was still using version 7.6). In general, there seems to be problems in parsing the line that starts #+begin_src lilypond. More specifically, - Global :noweb settings are now ignored - Any settings after the setting :file will be added to output file name! - Settings after :noweb yes cause trouble (disable this setting) Again, thanks for lisp/ob-lilypond.el in the first place. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 torsten.and...@beds.ac.uk http://strasheela.sourceforge.net http://www.torsten-anders.de
Re: [O] Babel: 1st version for music notation language Fomus
Dear Eric, On 8 Jul 2011, at 02:38, Eric Schulte wrote: > > Thanks for sharing this, it looks great, short clear and to the point. > > Shall I add it to the contrib/ directory? If you think it is already at that point, that is certainly fine by me. Best, Torsten > > Best -- Eric > > Torsten Anders writes: > >> Dear Babel developers, >> >> Inspired by the newly available Lilypond, I hacked up a first version >> of language support for Fomus >> (http://fomus.sourceforge.net/). Briefly, Fomus is a music notation >> system that translates a relatively simple domain specific music >> language into multiple output formats, including Lilypond and MusicXML >> (the latter is an open format supported by many commercial music >> notation systems such as Finale and Sibelius). In a nutshell, Fomus >> can simplify the generation of complex scores, because it can add >> various score information automatically. Anyway, please find my first >> attempt of a Fomus integration attached. >> >> This works already fine for standard code blocks such as the following. Note >> that the result of this is a Lilypond file. >> >> #+begin_src fomus :file test1.ly >> time 0 dur 2 pitch 60; >> time 2 dur 1 pitch 62; >> time 3 dur 1 pitch 63; >> time 4 dur 4 pitch 65; >> #+end_src >> >> Of course, because this is a quick hack, various improvements can be >> made. For example, it might be a good idea to allow for something like >> :file test.pdf, where the resulting Lilypond call would see file.ly, >> but the automatically inserted link in the org buffer would be the >> resulting file.pdf. >> >> Comments are welcome. >> >> Best wishes, >> Torsten >> >> -- >> Dr Torsten Anders >> Course Leader, Music Technology >> University of Bedfordshire >> Park Square, Room A315 >> http://strasheela.sourceforge.net >> http://www.torsten-anders.de >> >> >> >> >> >> >> > > -- > Eric Schulte > http://cs.unm.edu/~eschulte/ >
Re: [O] org-odt and bibliography
Dear Henri-Paul, On 8 Jul 2011, at 00:27, Henri-Paul Indiogine wrote: > Yes, but the sad thing is that using emacs+orgmode is so fast, easy > and productive. Writer or Word feel so clunky and backwards. Sure, you can write with orgmode and then export for your supervisor to OpenOffice/Word. I recently wrote a paper that way (before there was the now available export, using latex2rtf). Concerning references, I suggest for the draft you simply put in plain-text placeholders in (Author year) form. Your supervisor is probably happy with that at the drafting stage, and you can easily and quickly replace them later with whatever format you want, e.g., Zotero entries (you can even write your bibliography by hand, as your supervisor possibly does :). Best, Torsten
Re: [O] Org-babel: can evaluation confirmation be disabled (e.g., set to always yes)?
Dear Nick, > It is documented in the Org manual, sec. 14.5, Evaluating code blocks, > footnote 1, which points you to sec. 15.4, Code evaluation and security > issues. Thanks for your help (and apologies for missing this footnote). Best, Torsten
[O] Babel: 1st version for music notation language Fomus
Dear Babel developers, Inspired by the newly available Lilypond, I hacked up a first version of language support for Fomus (http://fomus.sourceforge.net/). Briefly, Fomus is a music notation system that translates a relatively simple domain specific music language into multiple output formats, including Lilypond and MusicXML (the latter is an open format supported by many commercial music notation systems such as Finale and Sibelius). In a nutshell, Fomus can simplify the generation of complex scores, because it can add various score information automatically. Anyway, please find my first attempt of a Fomus integration attached. This works already fine for standard code blocks such as the following. Note that the result of this is a Lilypond file. #+begin_src fomus :file test1.ly time 0 dur 2 pitch 60; time 2 dur 1 pitch 62; time 3 dur 1 pitch 63; time 4 dur 4 pitch 65; #+end_src Of course, because this is a quick hack, various improvements can be made. For example, it might be a good idea to allow for something like :file test.pdf, where the resulting Lilypond call would see file.ly, but the automatically inserted link in the org buffer would be the resulting file.pdf. Comments are welcome. Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://strasheela.sourceforge.net http://www.torsten-anders.de ob-fomus.el Description: Binary data
[O] Org-babel: can evaluation confirmation be disabled (e.g., set to always yes)?
Dear Babel developers, As you know, whenever I hit C-c C-c in a code block, I get the following question. Evaluate this code block on your system? (y or n) In the case of "nested" calls (using noweb) there can even be many queries like that before some code is actually executed. Can this be disabled by setting it to yes by default? I don't do any coding in my blocks that could in any ways adversely affect my system... I could not find anything related in the documentation, apologies if I missed it. Best, Torsten
[O] Thanks for Lilypond export (and minor comments)
Dear Martyn Jago, Congratulations to the Lilypond support included in the new Org version 7.6! For someone who uses both Org-mode and Lilypond anyway (like me :), this is great to have! Some brief comments. Support for additional languages like Lilypond and also awk should be celebrated by including them in the list of languages in the documentation (http://orgmode.org/org.html#Languages). I first had to load dot support (because you are calling org-babel-expand-body:dot). If you want to also attract musicians (without Org-programming experience themselves) it might be a good idea to very clearly document this dependency (or to remove it). Thank you! Best wishes, Torsten -- Dr Torsten Anders Course Leader, Music Technology University of Bedfordshire Park Square, Room A315 http://strasheela.sourceforge.net http://www.torsten-anders.de
Re: [Orgmode] Latex export of subtree not working for me
Dear Bastien, Thank you for your reply. This problem report is several months old, and I meanwhile resolved it. If I remember correctly, I reported the solution back. I think this problem was solved by updating to Aquamacs 2, but it is so long ago, I may misremember. But if not then it was something similarly simple... Again, thanks for checking. Best, Torsten On 2 Feb 2011, at 23:23, Bastien wrote: > Hi Torsten, > > "Torsten Anders" writes: > >> I would like to export only a subtree of an org file to PDF via Latex >> (ultimately using the package beamer). >> >> When doing export/publish (C-c C-e) I am given a menu with options, >> including the options "only export current subtree" and "publish >> enclosing subtree". If I choose any of these and then select a >> publishing command (e.g., export to Latex), then I get the following >> error. >> >> org-export: Symbol's function definition is void: activate-mark >> >> What am I missing? > > I can't reproduce this. Can you provide a backtrace? > > http://orgmode.org/manual/Feedback.html > > Thanks, > > -- > Bastien ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
Re: [Orgmode] Latex export of subtree not working for me
Dear David, > Looks like although Aquamacs 1.9 is based on Emacs 22, it lacks this > library. thank you very much for your helpful feedback. The problem is indeed solved with the latest version of Aquamacs (2.1), as I just found out. Best, Torsten >>> David Maus 20/09/10 7:29 PM >>> Torsten Anders wrote: >Dear all, >sorry for bothering you again with my question from a couple of days ago (see >below). >I would appreciate with someone could briefly confirm whether >exporting/publishing a subtree works for you (so I know whether the reported >problem is related to org mode or to my own Emacs configuration). >Thank you very much! >Best, >Torsten >-- >On Wed, 15 Sep 2010, Torsten Anders wrote >Dear all, >I would like to export only a subtree of an org file to PDF via Latex >(ultimately using the package beamer). >When doing export/publish (C-c C-e) I am given a menu with options, including >the options "only export current subtree" and "publish enclosing subtree". If >I choose any of these and then select a publishing command (e.g., export to >Latex), then I get the following error. > org-export: Symbol's function definition is void: activate-mark >What am I missing? >BTW: I am using the latest org mode version (just did git pull) with Aquamacs >1.9 on MacOS 10.5. Looks like a problem with Aquamacs to me: ,[ *Help* ] | activate-mark is a compiled Lisp function in `simple.el'. | | (activate-mark) | | Activate the mark. | | [back] ` The export fails because this function is not available. Looks like although Aquamacs 1.9 is based on Emacs 22, it lacks this library. You might try to check EmacsWiki for information about this issue: http://www.emacswiki.org/emacs/AquamacsEmacs Best, -- David -- OpenPGP... 0x99ADB83B5A4478E6 Jabber dmj...@jabber.org Email. dm...@ictsoc.de ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Latex export of subtree not working for me
Dear all, sorry for bothering you again with my question from a couple of days ago (see below). I would appreciate with someone could briefly confirm whether exporting/publishing a subtree works for you (so I know whether the reported problem is related to org mode or to my own Emacs configuration). Thank you very much! Best, Torsten -- On Wed, 15 Sep 2010, Torsten Anders wrote Dear all, I would like to export only a subtree of an org file to PDF via Latex (ultimately using the package beamer). When doing export/publish (C-c C-e) I am given a menu with options, including the options "only export current subtree" and "publish enclosing subtree". If I choose any of these and then select a publishing command (e.g., export to Latex), then I get the following error. org-export: Symbol's function definition is void: activate-mark What am I missing? BTW: I am using the latest org mode version (just did git pull) with Aquamacs 1.9 on MacOS 10.5. Thank you very much! Best Torsten Anders ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
[Orgmode] Latex export of subtree not working for me
Dear all, I would like to export only a subtree of an org file to PDF via Latex (ultimately using the package beamer). When doing export/publish (C-c C-e) I am given a menu with options, including the options "only export current subtree" and "publish enclosing subtree". If I choose any of these and then select a publishing command (e.g., export to Latex), then I get the following error. org-export: Symbol's function definition is void: activate-mark What am I missing? BTW: I am using the latest org mode version (just did git pull) with Aquamacs 1.9 on MacOS 10.5. Thank you very much! Best Torsten Anders ___ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
