Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
Hi Eric: Thanks a lot for your advice! It works for me now after I press C-c C-c on the #+PROPERTY line. It seems all my previous attempts fail because I didn't do C-c C-c. It would be nice if org can notice something changes in the header lines and do automatic refreshing when exporting. But anyway, the manual update C-c C-c works great as long as I can remember to do it. Thanks! Sincerely, Feiming Chen From: Eric Schulte eric.schu...@gmx.com To: Feiming Chen feimingc...@yahoo.com Cc: emacs-orgmode@gnu.org Sent: Fri, August 31, 2012 12:58:23 PM Subject: Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11] Feiming Chen feimingc...@yahoo.com writes: HI Eric: Thanks a lot! But I am still having trouble with some buffer-wide header arguments. In particular, I could not have the following code working as expected: #+PROPERTY: :eval no * test 3: Buffer-wide header arguments are NOT effective #+begin_src R :exports both print(pi) #+end_src I am getting the result printed even though I turned the evaluation off. It seems I could not turn off the evaluation with :eval no in the buffer-wide header argument. Could you help? Hi Feiming, I apologize. I gave you bad advice in my previous email. Please use the #+PROPERTY: setting as in your original email and as described in the Org-mode manual. Do *not* add a leading : to header argument names as I suggested. The following two Org-mode files both work as expected locally. If a buffer-wide header argument doesn't seem to be active, you can activate it by pressing C-c C-c on the #+PROPERTY: line. Cheers, Sincerely, Feiming Chen From: Eric Schulte eric.schu...@gmx.com To: Feiming Chen feimingc...@yahoo.com Cc: emacs-orgmode@gnu.org Sent: Thu, August 30, 2012 11:53:44 AM Subject: Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11] Feiming Chen feimingc...@yahoo.com writes: Hi: Could anyone help with the following problem? Please see the attached file a.org with its text export a.txt (from C-c C-e a). Replace #+PROPERTY: exports both #+PROPERTY: results output with #+PROPERTY: :exports both #+PROPERTY: :results output Best, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
HI Eric: Thanks a lot! But I am still having trouble with some buffer-wide header arguments. In particular, I could not have the following code working as expected: #+PROPERTY: :eval no * test 3: Buffer-wide header arguments are NOT effective #+begin_src R :exports both print(pi) #+end_src I am getting the result printed even though I turned the evaluation off. It seems I could not turn off the evaluation with :eval no in the buffer-wide header argument. Could you help? Sincerely, Feiming Chen From: Eric Schulte eric.schu...@gmx.com To: Feiming Chen feimingc...@yahoo.com Cc: emacs-orgmode@gnu.org Sent: Thu, August 30, 2012 11:53:44 AM Subject: Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11] Feiming Chen feimingc...@yahoo.com writes: Hi: Could anyone help with the following problem? Please see the attached file a.org with its text export a.txt (from C-c C-e a). Replace #+PROPERTY: exports both #+PROPERTY: results output with #+PROPERTY: :exports both #+PROPERTY: :results output Best, -- Eric Schulte http://cs.unm.edu/~eschulte
Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
Feiming Chen feimingc...@yahoo.com writes: HI Eric: Thanks a lot! But I am still having trouble with some buffer-wide header arguments. In particular, I could not have the following code working as expected: #+PROPERTY: :eval no * test 3: Buffer-wide header arguments are NOT effective #+begin_src R :exports both print(pi) #+end_src I am getting the result printed even though I turned the evaluation off. It seems I could not turn off the evaluation with :eval no in the buffer-wide header argument. Could you help? Hi Feiming, I apologize. I gave you bad advice in my previous email. Please use the #+PROPERTY: setting as in your original email and as described in the Org-mode manual. Do *not* add a leading : to header argument names as I suggested. The following two Org-mode files both work as expected locally. If a buffer-wide header argument doesn't seem to be active, you can activate it by pressing C-c C-c on the #+PROPERTY: line. #+PROPERTY: eval no #+begin_src R print(pi) #+end_src #+PROPERTY: exports both #+PROPERTY: results output * test 1: Buffer-wide header arguments are NOT effective #+begin_src R print(pi) #+end_src * test 1: Code block specific header arguments are effective #+begin_src R :exports both :results output print(pi) #+end_src Cheers, Sincerely, Feiming Chen From: Eric Schulte eric.schu...@gmx.com To: Feiming Chen feimingc...@yahoo.com Cc: emacs-orgmode@gnu.org Sent: Thu, August 30, 2012 11:53:44 AM Subject: Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11] Feiming Chen feimingc...@yahoo.com writes: Hi: Could anyone help with the following problem? Please see the attached file a.org with its text export a.txt (from C-c C-e a). Replace #+PROPERTY: exports both #+PROPERTY: results output with #+PROPERTY: :exports both #+PROPERTY: :results output Best, -- Eric Schulte http://cs.unm.edu/~eschulte
[O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
Hi: Could anyone help with the following problem? Please see the attached file a.org with its text export a.txt (from C-c C-e a). Test 1 is using buffer-wide header arguments BUT the evaluation result is not inserted into the exported file. I am following the Org Manual section 14.8.1 (Using header arguments). Test 2 is using code block specific header arguments and works as expected. For this test, I start emacs with emacs -Q, use org-version 7.8.11, and enabled Org Confirm Babel Evaluate and add R to Org Babel Load Languages. Thanks a lot for your help! Sincerely, Feiming Chen Emacs : GNU Emacs 24.1.1 (i686-pc-linux-gnu, GTK+ Version 2.22.0) of 2012-08-13 on fmc.work Package: Org-mode version 7.8.11 current state: == (setq org-export-blocks '((src org-babel-exp-src-block nil) (export-comment org-export-blocks-format-comment t) (ditaa org-export-blocks-format-ditaa nil) (dot org-export-blocks-format-dot nil)) org-ctrl-c-ctrl-c-hook '(org-babel-hash-at-point org-babel-execute-safely-maybe) org-export-preprocess-before-selecting-backend-code-hook '(org-beamer-select-beamer-code) org-tab-first-hook '(org-hide-block-toggle-maybe org-src-native-tab-command-maybe org-babel-hide-result-toggle-maybe) org-cycle-hook '(org-cycle-hide-archived-subtrees org-cycle-hide-drawers org-cycle-show-empty-lines org-optimize-window-after-visibility-change) org-agenda-before-write-hook '(org-agenda-add-entry-text) org-confirm-babel-evaluate nil org-speed-command-hook '(org-speed-command-default-hook org-babel-speed-command-hook) org-babel-pre-tangle-hook '(save-buffer) org-occur-hook '(org-first-headline-recenter) org-export-interblocks '((src org-babel-exp-non-block-elements)) org-metaup-hook '(org-babel-load-in-session-maybe) org-reveal-start-hook '(org-decrypt-entry) org-confirm-elisp-link-function 'yes-or-no-p org-export-latex-format-toc-function 'org-export-latex-format-toc-default org-export-preprocess-before-normalizing-links-hook '(org-remove-file-link-modifiers) org-clock-out-hook '(org-clock-remove-empty-clock-drawer) org-export-first-hook '(org-beamer-initialize-open-trackers) org-mode-hook '(#[nil \305\306\203 a = Author: Feiming Chen Date: 2012-08-30 11:27:38 EDT Table of Contents = 1 test 1: Buffer-wide header arguments are NOT effective 2 test 1: Code block specific header arguments are effective 1 test 1: Buffer-wide header arguments are NOT effective - print(pi) 2 test 1: Code block specific header arguments are effective - print(pi) [1] 3.141593 a.org Description: Binary data
Re: [O] Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
Feiming Chen feimingc...@yahoo.com writes: Hi: Could anyone help with the following problem? Please see the attached file a.org with its text export a.txt (from C-c C-e a). Replace #+PROPERTY: exports both #+PROPERTY: results output with #+PROPERTY: :exports both #+PROPERTY: :results output Best, -- Eric Schulte http://cs.unm.edu/~eschulte