[O] columnview with #+INCLUDE:, org-export-org?
Hello, I would like to capture the columnview of a file including the view of an org file specified using #+INCLUDE. These includes are currently only expanded during export so I am thinking maybe I should export to a temporary org buffer first and then do a columnview on the temporary buffer. Has anyone else already solved this problem? In particular, has anyone already done org-export-org? Any other comments, as I don't really know my way around the code too well yet. Thanks, Myles
Re: [O] capture - function-finding-location in TARGET: return value?
Hi, answering to myself: · Thomas Holst thomas.ho...@de.bosch.com wrote: Hello, I am trying to write a function to find the location where capture will put the captured item. The manual states, that a target configuration like : (file+function path/to/file function-finding-location) is possible. My question is, what is the function supposed to reurn? - a string with the headline - a location in the buffer - ... I looked into org-capture.el and experimented a little and so I found an answer: funtion-finding-location has to put point in the buffer of file at the desiered headline and return t if it was sucsessful. At least this works for my usecase. -- Mit freundlichen Grüßen / Best regards Thomas
Re: [O] columnview with #+INCLUDE:, org-export-org?
On Mon, 12 Mar 2012 10:40:44 +, Myles English said: Hello, I would like to capture the columnview of a file including the view of an org file specified using #+INCLUDE. These includes are currently only expanded during export so I am thinking maybe I should export to a temporary org buffer first and then do a columnview on the temporary buffer. Has anyone else already solved this problem? In particular, has anyone already done org-export-org? Any other comments, as I don't really know my way around the code too well yet. Thanks, Myles Turns out that everything is already included, and this works fine for my purposes: #+TITLE: test-include.org #+DATE: 2012-03-12 Mon #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: #+BEGIN_SRC emacs-lisp (org-export-as-org nil nil nil nil nil nil) (find-file test-include-source.org) (org-export-handle-include-files-recurse) #+END_SRC #+RESULTS: * Prologue #+INCLUDE: ./test-include-include.org :lines 19- * colview :noexport: #+BEGIN: columnview :hlines 5 :id file:test-include-source.org | Task | Effort | CLOCKSUM | |++--| | * Prologue || | |++--| | * Included heading || | #+END: #+TITLE: test-include-include.org #+AUTHOR:Myles English #+EMAIL: myles.engl...@ed.ac.uk #+DATE: 2012-03-12 Mon #+DESCRIPTION: #+KEYWORDS: #+LANGUAGE: en #+OPTIONS: H:3 num:t toc:t \n:nil @:t ::t |:t ^:t -:t f:t *:t :t #+OPTIONS: TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:not-in-toc #+INFOJS_OPT: view:nil toc:nil ltoc:t mouse:underline buttons:0 path:http://orgmode.org/org-info.js #+EXPORT_SELECT_TAGS: export #+EXPORT_EXCLUDE_TAGS: noexport #+LINK_UP: #+LINK_HOME: #+XSLT: * Don't want this heading included * Included heading This is included Thanks again for orgmode. Myles
Re: [O] android mobileorg: next week in agenda
Renato, not at this time... but if it's something that you'd like to see please open a feature request in our issue tracker on the github page: https://github.com/matburt/mobileorg-android/issues On Fri, Mar 9, 2012 at 1:39 PM, Renato renn...@gmail.com wrote: Hello, wasn't able to find an answer to this. Is it possible in the Android MobileOrg version, when viewing agenda, to go to next or previous week? I'm using version 0.8.3 best wishes, renato
[O] ways to insert note to self in an org-mode file for academic paper
I'm very early in trying a transition from LaTeX to org-mode for academic writing, trying to learn the Org way of doing things. Running Org-mode 7.7 in Emacs 23.4.1 on Win XP. Suppose I'm writing a draft of a research proposal and come to some part that I may want to consider changing, after I think about it some more, check with others, or reassess my resources. In LaTex, I'd write something like this: % need to look into this further, check with so-and-so and keep writing on the next line. How does one do this well in Org-mode? With a # comment character? Or does this become a TODO item? Of course, I wouldn't want that little note to self to appear in any final document. But I might want it to remain in the source file, to document my line of reasoning. Thanks. --Chris -- Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 425 Robinson Street, Binghamton, NY 13904 cryanatbinghamtondotedu Observation is a more powerful force than you could possibly reckon. The invisible, the overlooked, and the unobserved are the most in danger of reaching the end of the spectrum. They lose the last of their light. From there, anything can happen . . . [God, in Joan of Arcadia, episode entitled, The Uncertainty Principle.]
Re: [O] org babel execute shell in sh?
But I'm often bitten by the distinction between export and tangling -- :padline, :shebang come to mind, where I expected org-babel to honour the setting in both cases. Could you describe a use case where these options would be used for exporting and would be preferable to simply including the padding lines or the shebang literally in the code block? -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel][patch] Make ob-lilypond audition calls asynchronous
Applied, thanks. Martyn Jago martyn.j...@btinternet.com writes: Hi A patch to make ob-lilypond audition calls asynchronous (and tests). Best, Martyn From 2e7cd607cd6dbc25edd5ff9972fbd2528d48416e Mon Sep 17 00:00:00 2001 From: Martyn Jago martyn.j...@btinternet.com Date: Sat, 10 Mar 2012 15:00:57 + Subject: [PATCH] Make auditioning of midi and pdf generations asynchronous, and add easy pdf generation. * lisp/ob-lilypond.el: Make auditioning of midi and pdf asynchronous, and add easy pdf generation in the form of `ly-gen-pdf' variable. * testing/lisp/test-ob-lilypond.el: Tests for above. --- lisp/ob-lilypond.el | 68 ++--- testing/lisp/test-ob-lilypond.el | 22 +++- 2 files changed, 68 insertions(+), 22 deletions(-) diff --git a/lisp/ob-lilypond.el b/lisp/ob-lilypond.el index 0dde0de..fc9a639 100644 --- a/lisp/ob-lilypond.el +++ b/lisp/ob-lilypond.el @@ -3,7 +3,7 @@ ;; Copyright (C) 2010-2012 Free Software Foundation, Inc. ;; Author: Martyn Jago -;; Keywords: babel language, literate programming +;; Keywords: babel language, literate programming, music score ;; Homepage: https://github.com/mjago/ob-lilypond ;; This file is part of GNU Emacs. @@ -23,10 +23,14 @@ ;;; Commentary: -;; Installation / usage info, and examples are available at -;; https://github.com/mjago/ob-lilypond +;; Installation, ob-lilypond documentation, and examples are available at +;; http://orgmode.org/worg/org-contrib/babel/languages/ob-doc-lilypond.html +;; +;; Lilypond documentation can be found at +;; http://lilypond.org/manuals.html ;;; Code: + (require 'ob) (require 'ob-eval) (require 'ob-tangle) @@ -37,9 +41,11 @@ (add-to-list 'org-babel-tangle-lang-exts '(LilyPond . ly)) (defvar org-babel-default-header-args:lilypond '() - Default header arguments for js code blocks.) + Default header arguments for lilypond code blocks. +NOTE: The arguments are determined at lilypond compile time. +See (ly-set-header-args)) -(defconst ly-version 0.3 +(defconst ly-version 7.6 The version number of the file ob-lilypond.el.) (defvar ly-compile-post-tangle t @@ -86,6 +92,10 @@ LY-GEN-SVG to t) HTML generation can be turned on by default by setting LY-GEN-HTML to t) +(defvar ly-gen-pdf nil +PDF generation can be turned on by default by setting +LY-GEN-PDF to t) + (defvar ly-use-eps nil You can force the compiler to use the EPS backend by setting LY-USE-EPS to t) @@ -203,18 +213,20 @@ FILE-NAME is full path to lilypond (.ly) file (arg-2 nil);infile (arg-3 *lilypond*) ;buffer (arg-4 t) ;display -(arg-5 (if ly-gen-png --png )) ;rest... - (arg-6 (if ly-gen-html --html )) -(arg-7 (if ly-use-eps -dbackend=eps )) -(arg-8 (if ly-gen-svg -dbackend=svg )) -(arg-9 (concat --output= (file-name-sans-extension file-name))) -(arg-10 file-name)) + (arg-4 t) ;display + (arg-5 (if ly-gen-png --png )) ;rest... + (arg-6 (if ly-gen-html --html )) +(arg-7 (if ly-gen-pdf --pdf )) +(arg-8 (if ly-use-eps -dbackend=eps )) +(arg-9 (if ly-gen-svg -dbackend=svg )) +(arg-10 (concat --output= (file-name-sans-extension file-name))) +(arg-11 file-name)) (if test -`(,arg-1 ,arg-2 ,arg-3 ,arg-4 ,arg-5 - ,arg-6 ,arg-7 ,arg-8 ,arg-9 ,arg-10) +`(,arg-1 ,arg-2 ,arg-3 ,arg-4 ,arg-5 ,arg-6 + ,arg-7 ,arg-8 ,arg-9 ,arg-10, arg-11) (call-process - arg-1 arg-2 arg-3 arg-4 arg-5 - arg-6 arg-7 arg-8 arg-9 arg-10 + arg-1 arg-2 arg-3 arg-4 arg-5 arg-6 + arg-7 arg-8 arg-9 arg-10 arg-11 (defun ly-check-for-compile-error (file-name optional test) Check for compile error. @@ -307,8 +319,12 @@ If TEST is non-nil, the shell command is returned and is not run (concat (ly-determine-pdf-path) pdf-file))) (if test cmd-string - (shell-command cmd-string))) -(message No pdf file generated so can't display!) + (start-process +\Audition pdf\ +*lilypond* +(ly-determine-pdf-path) +pdf-file))) + (message No pdf file generated so can't display!) (defun ly-attempt-to-play-midi (file-name optional test) Attempt to play the generated MIDI file @@ -322,7 +338,11 @@ If TEST is non-nil, the shell command is returned and is not run (concat (ly-determine-midi-path) midi-file))) (if test cmd-string - (shell-command cmd-string))) + (start-process + \Audition midi\ + *lilypond* + (ly-determine-midi-path) +
Re: [O] Blank first line in a tangled file prevents src block execution
Nick Dokos nicholas.do...@hp.com writes: Eric Schulte eric.schu...@gmx.com wrote: Or try #+begin_src sh :tangle code/get_wavs.sh :shebang #!/bin/bash for fn_in in $@; do fn_out=$(sed -e 's|\.3gp$||g' -e 's|$|.wav|g' $fn_in) ffmpeg -i $fn_in -vn -f wav -acodec pcm_u8 $fn_out done #+end_src That reminds me: I believe shebang is used in tangling, but not in evaluation. Assuming that's correct, is there any fundamental reason for it not being used in evaluation? Shell code blocks are evaluated using the org-babel-sh-command variable. When the executing command is explicitly provided there is no need for a shebang line, and it would be (to my knowledge) ignored. Best, -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] [babel] Bug with empty results
Fixed, Thanks for the report. t...@tsdye.com (Thomas S. Dye) writes: Aloha all, BEGIN and END are transposed with empty results, as shown in the example below. The results shown are from two evaluations of the source code block. I'm using Org-mode version 7.8.03 (release_7.8.03.575.g06a1b) All the best, Tom * Empty results #+begin_src emacs-lisp :results silent (org-babel-do-load-languages 'org-babel-load-languages '((R . t) )) #+end_src #+name: show-bug #+header: :results output replace org #+BEGIN_SRC R #+END_SRC #+results: show-bug #+END_ORG #+BEGIN_ORG #+END_ORG #+BEGIN_ORG -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] ways to insert note to self in an org-mode file for academic paper
On Mon, 12 Mar 2012 11:55:23 -0400, Christopher W Ryan said: I'm very early in trying a transition from LaTeX to org-mode for academic writing, trying to learn the Org way of doing things. Running Org-mode 7.7 in Emacs 23.4.1 on Win XP. Suppose I'm writing a draft of a research proposal and come to some part that I may want to consider changing, after I think about it some more, check with others, or reassess my resources. In LaTex, I'd write something like this: % need to look into this further, check with so-and-so and keep writing on the next line. How does one do this well in Org-mode? With a # comment character? Or does this become a TODO item? Chris, I use inline tasks. e.g. *** TODO look into this further, check with so-and-so *** END And to see all of the todos in the file I use this quite a lot, just press F9 to see a list: ;; show all todos in the current buffer with one key press (global-set-key (kbd f9) (lambda () (interactive) (org-agenda nil t 'file))) Of course, I wouldn't want that little note to self to appear in any final document. But I might want it to remain in the source file, to document my line of reasoning. To not export todos, have this at the top of you file and press C-c on it before exporting: #+OPTIONS: todo:nil Thanks. --Chris -- Christopher W. Ryan, MD SUNY Upstate Medical University Clinical Campus at Binghamton 425 Robinson Street, Binghamton, NY 13904 cryanatbinghamtondotedu Observation is a more powerful force than you could possibly reckon. The invisible, the overlooked, and the unobserved are the most in danger of reaching the end of the spectrum. They lose the last of their light. From there, anything can happen . . . [God, in Joan of Arcadia, episode entitled, The Uncertainty Principle.] Myles
Re: [O] org babel execute shell in sh?
Eric Schulte eric.schu...@gmx.com writes: But I'm often bitten by the distinction between export and tangling -- :padline, :shebang come to mind, where I expected org-babel to honour the setting in both cases. Could you describe a use case where these options would be used for exporting and would be preferable to simply including the padding lines or the shebang literally in the code block? I use an LP org-document with zsh-codefragments to generate a CLIF testplan - the script is tangled, then executed and the output -- the generated .ctp file -- exported. In this case I'd prefere it to have the shell from the :shebang option used to run the tangled program, not /bin/sh, so that exporting the output inside the document and running the tangled program standalone produce the same result. At the moment I have to set the shell document- or session-wide to zsh to get reproducible behaviour. Whenever the export/execution is part of the generated document and of the generated product (the tangled code) I would like it, not to have to sides to configure. I don't know, if I make myself clear -- If not, please tell me so and I try to distill an example out of the cases I encountered at work, where I was wondering why some things did not work as I expected. Kind regards, Tom
Re: [O] org babel execute shell in sh?
Tom Regner t...@goochesa.de writes: Eric Schulte eric.schu...@gmx.com writes: But I'm often bitten by the distinction between export and tangling -- :padline, :shebang come to mind, where I expected org-babel to honour the setting in both cases. Could you describe a use case where these options would be used for exporting and would be preferable to simply including the padding lines or the shebang literally in the code block? I use an LP org-document with zsh-codefragments to generate a CLIF testplan - the script is tangled, then executed and the output -- the generated .ctp file -- exported. In this case I'd prefere it to have the shell from the :shebang option used to run the tangled program, not /bin/sh, so that exporting the output inside the document and running the tangled program standalone produce the same result. At the moment I have to set the shell document- or session-wide to zsh to get reproducible behaviour. Whenever the export/execution is part of the generated document and of the generated product (the tangled code) I would like it, not to have to sides to configure. I don't know, if I make myself clear -- If not, please tell me so and I try to distill an example out of the cases I encountered at work, where I was wondering why some things did not work as I expected. I think I understand now, so it is execution not export behavior which could make use of the :shebang header argument. I suppose that it would be possible to allow the :shebang header argument to silently override the value of the `org-babel-sh-command' variable when it is present. I just pushed up a patch which adds this behavior. It does result in some odd new possibilities, such as the following. #+begin_src sh :shebang #!/bin/cat foo #+end_src #+RESULTS: | #!/bin/cat | || | foo| Best, Kind regards, Tom -- Eric Schulte http://cs.unm.edu/~eschulte/
Re: [O] org babel execute shell in sh?
Eric Schulte eric.schu...@gmx.com wrote:
I just pushed up a patch which adds this behavior. It does result in
some odd new possibilities, such as the following.
#+begin_src sh :shebang #!/bin/cat
foo
#+end_src
#+RESULTS:
| #!/bin/cat |
||
| foo|
Maybe my settings are slightly different, but the new bits give me
,
| #+begin_src sh :shebang #!/bin/cat
| foo
| #+end_src
|
| #+RESULTS:
| : foo
`
They also give me sensible results with the original example:
,
| #+begin_src sh :shebang #!/bin/bash
| for np in {1..32}
| do
| echo $np
| done
| #+end_src
|
| #+RESULTS:
| | 1 |
| | 2 |
| | 3 |
| |... |
| | 31 |
| | 32 |
`
The only potentially confusing case I've found is the following:
,
| #+begin_src sh
| #!/bin/bash
| for np in {1..32}
| do
| echo $np
| done
| #+end_src
|
| #+RESULTS:
| : {1..32}
`
with the shebang as part of the script. I'd argue it's doing the right
thing however: if one remembers that sh is the default command, this is
equivalent to the command line invocation:
,
| $ sh foo.sh
`
where foo.sh contains
--8---cut here---start-8---
#!/bin/bash
for np in {1..32}
do
echo $np
done
--8---cut here---end---8---
and that too gives:
,
| $ sh foo.sh
| {1..32}
`
whereas
,
| $ ./foo.sh
| 1
| 2
| 3
| ...
| 31
| 32
`
In other words, sh does not interpret the shebang: that is only done
by the exec system call.
Nick
Re: [O] issue with babel R evaluate session vs external process
finally I found the problem: it was not at all related to org or babel, but due to a function in my ess-send-input-hook. sorry for bothering :) Thomas Alexander Gerds tagt...@sund.ku.dk writes: still a beginner, and maybe therefore, in my setup (release is: 7.8.03, emacs 23.2.1) the following occurs -org.snip--- * here it works: org-ctrl-c-ctrl-c and export #+begin_src R :results output :exports results foo=matrix(1:2) foo #+end_src #+RESULTS: : [,1] : [1,]1 : [2,]2 * here it does not: #+begin_src R :results output :exports results :session *R* foo=matrix(3:8) foo #+end_src the buffer *R* shows this: 'org_babel_R_eoe' [1] org_babel_R_eoe org.snap-- some debugging revealed this: ELISP (org-babel-R-evaluate-session *R* foo=matrix(1:2)\nfoo output '(output replace) nil nil) *** Eval error *** ELISP (org-babel-R-evaluate-external-process foo=matrix(1:2)\nfoo output '(output replace) nil nil) [,1]\n[1,]1\n[2,]2\n but strange-enough when I try to edebug org-babel-R-evaluate-session, I get an error: Symbol's value as variable is void: edebug-after can someone explain this? thanks! tomy -- Thomas A. Gerds -- Assoc. Prof. Department of Biostatistics University of Copenhagen, Øster Farimagsgade 5, 1014 Copenhagen, Denmark Office: CSS-15.2.07 (Gamle Kommunehospital) tel: 35327914 (sec: 35327901)
[O] Beamer specific setupfile?
I use beamer a lot for work and decided to create a beamer-specific
setupfile to clean up my org files a bit. My files typically contain a
header like so:
---
#+latex_class: beamer
#+startup: beamer
#+options: toc:nil latex:t tex:t
#+latex_class_options: [presentation,bigger]
#+beamer_frame_level: 1
#+beamer_header_extra:
\usetheme[alternativetitlepage=true,titleline=true,titlepagelogo=../pics/pic.jpg]{Torino}
#+beamer_header_extra: \usecolortheme{freewilly}
#+latex_header: \usepackage{tikz}
#+latex_header:
\usetikzlibrary{decorations,arrows,automata,positioning,backgrounds}
#+latex_header: \usepackage{setspace}
#+latex_header: \setstretch{1.3}
#+latex_header: \usepackage{lmodern}
#+latex_header: \usepackage{booktabs}
#+AUTHOR:John Henderson
---
I tried inserting the above into a file called =beamer-setup.org= and
simply doing:
---
#+setupfile: ~/org/aux/beamer-setup.org
---
This doesn't seem to work, however. My theme doesn't get picked up,
for example. If I put the contents into the file directly, I'm all
set. Any suggestions on why this might be the case?
Thanks,
John
[O] [PATCH] org-attach-store-link-p gets wrong value for attach when using customize-variable
Hi, I have attached a very small patch fixing the value that org-attach-store-link-p gets through the customize interface. The additional quote prevented org-attach-attach from calling org-attach-store-link when org-attach-store-link-p was configured to Link to the attach-dir location. best regards, Henning Weiss diff --git a/lisp/org-attach.el b/lisp/org-attach.el index 1816a07..7ba3d72 100644 --- a/lisp/org-attach.el +++ b/lisp/org-attach.el @@ -105,7 +105,7 @@ lncreate a hard link. Note that this is not supported :type '(choice (const :tag Don't store link nil) (const :tag Link to origin location t) - (const :tag Link to the attach-dir location 'attached))) + (const :tag Link to the attach-dir location attached))) ;;;###autoload (defun org-attach ()
Re: [O] Beamer specific setupfile?
John Hendy jw.he...@gmail.com wrote:
I use beamer a lot for work and decided to create a beamer-specific
setupfile to clean up my org files a bit. My files typically contain a
header like so:
---
#+latex_class: beamer
#+startup: beamer
#+options: toc:nil latex:t tex:t
#+latex_class_options: [presentation,bigger]
#+beamer_frame_level: 1
#+beamer_header_extra:
\usetheme[alternativetitlepage=true,titleline=true,titlepagelogo=../pics/pic.jpg]{Torino}
#+beamer_header_extra: \usecolortheme{freewilly}
#+latex_header: \usepackage{tikz}
#+latex_header:
\usetikzlibrary{decorations,arrows,automata,positioning,backgrounds}
#+latex_header: \usepackage{setspace}
#+latex_header: \setstretch{1.3}
#+latex_header: \usepackage{lmodern}
#+latex_header: \usepackage{booktabs}
#+AUTHOR:John Henderson
---
I tried inserting the above into a file called =beamer-setup.org= and
simply doing:
---
#+setupfile: ~/org/aux/beamer-setup.org
---
This doesn't seem to work, however. My theme doesn't get picked up,
for example. If I put the contents into the file directly, I'm all
set. Any suggestions on why this might be the case?
C-c C-c on the setupfile line? The doc says
,
| `#+SETUPFILE: file'
| This line defines a file that holds more in-buffer setup.
| Normally this is entirely ignored. Only when the buffer is parsed
| for option-setting lines (i.e. when starting Org mode for a file,
| when pressing `C-c C-c' in a settings line, or when exporting),
| then the contents of this file are parsed as if they had been
| included in the buffer. In particular, the file can be any other
| Org mode file with internal setup. You can visit the file the
| cursor is in the line with `C-c ''.
`
and when I try the export, it fails to find freewilly.sty (no surprise
there), which seems to show that the file *is* processed.
Nick
Re: [O] Beamer specific setupfile?
John Hendy jw.he...@gmail.com wrote:
#+beamer_header_extra: \usecolortheme{freewilly}
Correction: the error I get is
,
| ! LaTeX Error: File `beamercolorthemefreewilly.sty' not found.
`
Nick
Re: [O] Beamer specific setupfile?
John Hendy jw.he...@gmail.com wrote:
I use beamer a lot for work and decided to create a beamer-specific
setupfile to clean up my org files a bit. My files typically contain a
header like so:
---
#+latex_class: beamer
#+startup: beamer
#+options: toc:nil latex:t tex:t
#+latex_class_options: [presentation,bigger]
#+beamer_frame_level: 1
#+beamer_header_extra:
\usetheme[alternativetitlepage=true,titleline=true,titlepagelogo=../pics/pic.jpg]{Torino}
#+beamer_header_extra: \usecolortheme{freewilly}
Actually all the #+BEAMER_* options are ignored (I fixed the line
breaks, so that's not it). Everything else makes it into the tex file.
Seems something is broke.
Nick
#+latex_header: \usepackage{tikz}
#+latex_header:
\usetikzlibrary{decorations,arrows,automata,positioning,backgrounds}
#+latex_header: \usepackage{setspace}
#+latex_header: \setstretch{1.3}
#+latex_header: \usepackage{lmodern}
#+latex_header: \usepackage{booktabs}
#+AUTHOR:John Henderson
---
I tried inserting the above into a file called =beamer-setup.org= and
simply doing:
---
#+setupfile: ~/org/aux/beamer-setup.org
---
This doesn't seem to work, however. My theme doesn't get picked up,
for example. If I put the contents into the file directly, I'm all
set. Any suggestions on why this might be the case?
Thanks,
John
Re: [O] Beamer specific setupfile?
On Mon, Mar 12, 2012 at 4:48 PM, Nick Dokos nicholas.do...@hp.com wrote:
John Hendy jw.he...@gmail.com wrote:
I use beamer a lot for work and decided to create a beamer-specific
setupfile to clean up my org files a bit. My files typically contain a
header like so:
---
#+latex_class: beamer
#+startup: beamer
#+options: toc:nil latex:t tex:t
#+latex_class_options: [presentation,bigger]
#+beamer_frame_level: 1
#+beamer_header_extra:
\usetheme[alternativetitlepage=true,titleline=true,titlepagelogo=../pics/pic.jpg]{Torino}
#+beamer_header_extra: \usecolortheme{freewilly}
#+latex_header: \usepackage{tikz}
#+latex_header:
\usetikzlibrary{decorations,arrows,automata,positioning,backgrounds}
#+latex_header: \usepackage{setspace}
#+latex_header: \setstretch{1.3}
#+latex_header: \usepackage{lmodern}
#+latex_header: \usepackage{booktabs}
#+AUTHOR: John Henderson
---
I tried inserting the above into a file called =beamer-setup.org= and
simply doing:
---
#+setupfile: ~/org/aux/beamer-setup.org
---
This doesn't seem to work, however. My theme doesn't get picked up,
for example. If I put the contents into the file directly, I'm all
set. Any suggestions on why this might be the case?
C-c C-c on the setupfile line? The doc says
,
| `#+SETUPFILE: file'
| This line defines a file that holds more in-buffer setup.
| Normally this is entirely ignored. Only when the buffer is parsed
| for option-setting lines (i.e. when starting Org mode for a file,
| when pressing `C-c C-c' in a settings line, or when exporting),
| then the contents of this file are parsed as if they had been
| included in the buffer. In particular, the file can be any other
| Org mode file with internal setup. You can visit the file the
| cursor is in the line with `C-c ''.
`
and when I try the export, it fails to find freewilly.sty (no surprise
there), which seems to show that the file *is* processed.
Yeah, I should have just posted an example with an included theme
instead of the one I usually use. I think I tracked it down. First, I
added =t= to the list of class options:
---
#+latex_class_options: [t,presentation,bigger]
---
I saw an effect on my frame alignment, which told me things were,
indeed, being read. It seems the issue was with using
#+beamer_header_extra. I don't know what that's supposed to be for,
but it isn't picking up the theme option. Actually... in searching for
what it's supposed to be used for, I ran across a mailing list post of
the same problem:
-- http://lists.gnu.org/archive/html/emacs-orgmode/2010-09/msg01011.html
Indeed, ditching beamer_header_extra for the theme setting and just
using #+latex_header... works.
Thoughts on fixing this?
John
Nick
Re: [O] Beamer specific setupfile?
John Hendy jw.he...@gmail.com wrote:
On Mon, Mar 12, 2012 at 4:48 PM, Nick Dokos nicholas.do...@hp.com wrote:
John Hendy jw.he...@gmail.com wrote:
I use beamer a lot for work and decided to create a beamer-specific
setupfile to clean up my org files a bit. My files typically contain a
header like so:
---
#+latex_class: beamer
#+startup: beamer
#+options: toc:nil latex:t tex:t
#+latex_class_options: [presentation,bigger]
#+beamer_frame_level: 1
#+beamer_header_extra:
\usetheme[alternativetitlepage=true,titleline=true,titlepagelogo=../pics/pic.jpg]{Torino}
#+beamer_header_extra: \usecolortheme{freewilly}
#+latex_header: \usepackage{tikz}
#+latex_header:
\usetikzlibrary{decorations,arrows,automata,positioning,backgrounds}
#+latex_header: \usepackage{setspace}
#+latex_header: \setstretch{1.3}
#+latex_header: \usepackage{lmodern}
#+latex_header: \usepackage{booktabs}
#+AUTHOR: John Henderson
---
I tried inserting the above into a file called =beamer-setup.org= and
simply doing:
---
#+setupfile: ~/org/aux/beamer-setup.org
---
This doesn't seem to work, however. My theme doesn't get picked up,
for example. If I put the contents into the file directly, I'm all
set. Any suggestions on why this might be the case?
C-c C-c on the setupfile line? The doc says
,
| `#+SETUPFILE: file'
| This line defines a file that holds more in-buffer setup.
| Normally this is entirely ignored. Only when the buffer is parsed
| for option-setting lines (i.e. when starting Org mode for a file,
| when pressing `C-c C-c' in a settings line, or when exporting),
| then the contents of this file are parsed as if they had been
| included in the buffer. In particular, the file can be any other
| Org mode file with internal setup. You can visit the file the
| cursor is in the line with `C-c ''.
`
and when I try the export, it fails to find freewilly.sty (no surprise
there), which seems to show that the file *is* processed.
Yeah, I should have just posted an example with an included theme
instead of the one I usually use. I think I tracked it down. First, I
added =t= to the list of class options:
---
#+latex_class_options: [t,presentation,bigger]
---
I saw an effect on my frame alignment, which told me things were,
indeed, being read. It seems the issue was with using
#+beamer_header_extra. I don't know what that's supposed to be for,
but it isn't picking up the theme option. Actually... in searching for
what it's supposed to be used for, I ran across a mailing list post of
the same problem:
-- http://lists.gnu.org/archive/html/emacs-orgmode/2010-09/msg01011.html
Indeed, ditching beamer_header_extra for the theme setting and just
using #+latex_header... works.
Thoughts on fixing this?
The beamer exporter is searching the original file for #+BEAMER_* stuff, not
the setup file (and of course it does not find anything interesting there).
The latex exporter seems to find everything in the setup file however, so there
must be some mechanism for searching the setup file. If so, it should be
possible to crib it and copy it into the beamer exporter. But the devil, as the
saying goes, is in the details...
Nick
Re: [O] Beamer specific setupfile?
Nick Dokos nicholas.do...@hp.com wrote: Yeah, I should have just posted an example with an included theme instead of the one I usually use. I think I tracked it down. First, I added =t= to the list of class options: --- #+latex_class_options: [t,presentation,bigger] --- I saw an effect on my frame alignment, which told me things were, indeed, being read. It seems the issue was with using #+beamer_header_extra. I don't know what that's supposed to be for, but it isn't picking up the theme option. Actually... in searching for what it's supposed to be used for, I ran across a mailing list post of the same problem: -- http://lists.gnu.org/archive/html/emacs-orgmode/2010-09/msg01011.html Indeed, ditching beamer_header_extra for the theme setting and just using #+latex_header... works. Thoughts on fixing this? The beamer exporter is searching the original file for #+BEAMER_* stuff, not the setup file (and of course it does not find anything interesting there). The latex exporter seems to find everything in the setup file however, so there must be some mechanism for searching the setup file. If so, it should be possible to crib it and copy it into the beamer exporter. But the devil, as the saying goes, is in the details... I think the magic for latex headers happens in org-infile-export-plist: but the function has not been told about #+BEAMER_* stuff, so it'll need the addition of a few more cases to handle the beamer stuff. Nick
Re: [O] Beamer specific setupfile?
[I think I broke the thread - so let me try again] John Hendy jw.he...@gmail.com wrote: Yeah, I should have just posted an example with an included theme instead of the one I usually use. I think I tracked it down. First, I added =t= to the list of class options: --- #+latex_class_options: [t,presentation,bigger] --- I saw an effect on my frame alignment, which told me things were, indeed, being read. It seems the issue was with using #+beamer_header_extra. I don't know what that's supposed to be for, but it isn't picking up the theme option. Actually... in searching for what it's supposed to be used for, I ran across a mailing list post of the same problem: -- http://lists.gnu.org/archive/html/emacs-orgmode/2010-09/msg01011.html Indeed, ditching beamer_header_extra for the theme setting and just using #+latex_header... works. Thoughts on fixing this? Nick Dokos nicholas.do...@hp.com wrote: The beamer exporter is searching the original file for #+BEAMER_* stuff, not the setup file (and of course it does not find anything interesting there). The latex exporter seems to find everything in the setup file however, so there must be some mechanism for searching the setup file. If so, it should be possible to crib it and copy it into the beamer exporter. But the devil, as the saying goes, is in the details... I think the magic for latex headers happens in org-infile-export-plist: but the function has not been told about #+BEAMER_* stuff, so it'll need the addition of a few more cases to handle the beamer stuff. Nick
Re: [O] Unable to find contrib/
Thanks for all your help. I could solve the issue. The org-root-directory needed to be specified, in my case ~/bin/org-7.8.03/. I overlooked that fact- and all of your response helped. Deb On Sun, Mar 11, 2012 at 3:27 AM, Debaditya Mukhopadhyay debadi...@gmail.com wrote: I have org 7.8.03. added to my .emacs (add-to-list 'load-path org-root-dir/contrib/lisp) (require 'org-mime) getting File error: Cannot open load file, org-mime To ensure normal operation, you should investigate and remove the cause of the error in your initialization file. Start Emacs with the `--debug-init' option to view a complete error backtrace. Any help will be appreciated.
Re: [O] [babel] Bug with empty results
Works here. Thanks. Tom Eric Schulte eric.schu...@gmx.com writes: Fixed, Thanks for the report. t...@tsdye.com (Thomas S. Dye) writes: Aloha all, BEGIN and END are transposed with empty results, as shown in the example below. The results shown are from two evaluations of the source code block. I'm using Org-mode version 7.8.03 (release_7.8.03.575.g06a1b) All the best, Tom * Empty results #+begin_src emacs-lisp :results silent (org-babel-do-load-languages 'org-babel-load-languages '((R . t) )) #+end_src #+name: show-bug #+header: :results output replace org #+BEGIN_SRC R #+END_SRC #+results: show-bug #+END_ORG #+BEGIN_ORG #+END_ORG #+BEGIN_ORG -- Thomas S. Dye http://www.tsdye.com
[O] ITEM special property
Is the following correct: - the ITEM special property returns the _headline_ of an entry (not the content); - ITEM can't be used in tag/match queries, only in column view formats. thanks, ilya
Re: [O] Beamer specific setupfile?
On Mon, Mar 12, 2012 at 5:44 PM, Nick Dokos nicholas.do...@hp.com wrote: Nick Dokos nicholas.do...@hp.com wrote: Yeah, I should have just posted an example with an included theme instead of the one I usually use. I think I tracked it down. First, I added =t= to the list of class options: --- #+latex_class_options: [t,presentation,bigger] --- I saw an effect on my frame alignment, which told me things were, indeed, being read. It seems the issue was with using #+beamer_header_extra. I don't know what that's supposed to be for, but it isn't picking up the theme option. Actually... in searching for what it's supposed to be used for, I ran across a mailing list post of the same problem: -- http://lists.gnu.org/archive/html/emacs-orgmode/2010-09/msg01011.html Indeed, ditching beamer_header_extra for the theme setting and just using #+latex_header... works. Thoughts on fixing this? The beamer exporter is searching the original file for #+BEAMER_* stuff, not the setup file (and of course it does not find anything interesting there). The latex exporter seems to find everything in the setup file however, so there must be some mechanism for searching the setup file. If so, it should be possible to crib it and copy it into the beamer exporter. But the devil, as the saying goes, is in the details... I think the magic for latex headers happens in org-infile-export-plist: but the function has not been told about #+BEAMER_* stuff, so it'll need the addition of a few more cases to handle the beamer stuff. Nick Great. Thanks for checking into this. I don't know how to fix it, so I'll simply stick to #+latex_header, as this is working fine at the moment. It's interesting that #+beamer_ options work from the file itself, but not from the setupfile, considering it sounds like all the setupfile line does it treat the contents as if it's in the file itself. Something's getting lost in there. Thanks again, John
Re: [O] Beamer specific setupfile?
John Hendy jw.he...@gmail.com wrote: I think the magic for latex headers happens in org-infile-export-plist: but the function has not been told about #+BEAMER_* stuff, so it'll need the addition of a few more cases to handle the beamer stuff. Great. Thanks for checking into this. I don't know how to fix it, so I'll simply stick to #+latex_header, as this is working fine at the moment. It's interesting that #+beamer_ options work from the file itself, but not from the setupfile, considering it sounds like all the setupfile line does it treat the contents as if it's in the file itself. Something's getting lost in there. org-infile-export-plist parses the current buffer and takes care of #+SETUPFILE: options (even recursive ones). It constructs an options property list and returns it. The latex exporter stashes it into org-export-latex-options-plist which is then consulted by the exporter (in all cases, including the beamer case). The trouble is that org-infile-export-plist does not know about #+BEAMER_HEADER_EXTRA or #+BEAMER_FRAME_LEVEL, so it does not put them in the plist it returns. It is a trivial thing to add them however: they are exactly analogous to LATEX_HEADER and LATEX_CLASS options, both of which org-infile-export-plist handles fine. Nick
