* Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
@ 2012-08-30 15:39 Feiming Chen
2012-08-30 15:53 ` Eric Schulte
0 siblings, 1 reply; 5+ messages in thread
From: Feiming Chen @ 2012-08-30 15:39 UTC (permalink / raw)
To: emacs-orgmode
[-- Attachment #1.1: Type: text/plain, Size: 2419 bytes --]
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
[-- Attachment #1.2: Type: text/html, Size: 3394 bytes --]
[-- Attachment #2: a.txt --]
[-- Type: text/plain, Size: 573 bytes --]
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
[-- Attachment #3: a.org --]
[-- Type: application/octet-stream, Size: 282 bytes --]
#+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
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
2012-08-30 15:39 Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11] Feiming Chen
@ 2012-08-30 15:53 ` Eric Schulte
2012-08-31 16:38 ` Feiming Chen
0 siblings, 1 reply; 5+ messages in thread
From: Eric Schulte @ 2012-08-30 15:53 UTC (permalink / raw)
To: Feiming Chen; +Cc: emacs-orgmode
Feiming Chen <feimingchen@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
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
2012-08-30 15:53 ` Eric Schulte
@ 2012-08-31 16:38 ` Feiming Chen
2012-08-31 16:57 ` Eric Schulte
0 siblings, 1 reply; 5+ messages in thread
From: Feiming Chen @ 2012-08-31 16:38 UTC (permalink / raw)
To: Eric Schulte; +Cc: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 1183 bytes --]
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.schulte@gmx.com>
To: Feiming Chen <feimingchen@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 <feimingchen@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
[-- Attachment #2: Type: text/html, Size: 2279 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread* Re: Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
2012-08-31 16:38 ` Feiming Chen
@ 2012-08-31 16:57 ` Eric Schulte
2012-09-04 21:26 ` Feiming Chen
0 siblings, 1 reply; 5+ messages in thread
From: Eric Schulte @ 2012-08-31 16:57 UTC (permalink / raw)
To: Feiming Chen; +Cc: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 1011 bytes --]
Feiming Chen <feimingchen@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.
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: eval.org --]
[-- Type: text/x-org, Size: 57 bytes --]
#+PROPERTY: eval no
#+begin_src R
print(pi)
#+end_src
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #3: a.org --]
[-- Type: text/x-org, Size: 282 bytes --]
#+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
[-- Attachment #4: Type: text/plain, Size: 748 bytes --]
Cheers,
>
>
> Sincerely,
> Feiming Chen
>
>
>
>
> ________________________________
> From: Eric Schulte <eric.schulte@gmx.com>
> To: Feiming Chen <feimingchen@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 <feimingchen@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
^ permalink raw reply [flat|nested] 5+ messages in thread
* Re: Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11]
2012-08-31 16:57 ` Eric Schulte
@ 2012-09-04 21:26 ` Feiming Chen
0 siblings, 0 replies; 5+ messages in thread
From: Feiming Chen @ 2012-09-04 21:26 UTC (permalink / raw)
To: Eric Schulte; +Cc: emacs-orgmode
[-- Attachment #1: Type: text/plain, Size: 2473 bytes --]
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.schulte@gmx.com>
To: Feiming Chen <feimingchen@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 <feimingchen@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.schulte@gmx.com>
> To: Feiming Chen <feimingchen@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 <feimingchen@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
[-- Attachment #2: Type: text/html, Size: 4206 bytes --]
^ permalink raw reply [flat|nested] 5+ messages in thread
end of thread, other threads:[~2012-09-04 21:26 UTC | newest]
Thread overview: 5+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2012-08-30 15:39 Bug: BABEL Buffer-wide header arguments are NOT effective [7.8.11] Feiming Chen
2012-08-30 15:53 ` Eric Schulte
2012-08-31 16:38 ` Feiming Chen
2012-08-31 16:57 ` Eric Schulte
2012-09-04 21:26 ` Feiming Chen
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).