[O] Org-Export Subtree Options Not Working
When I input subtree options for modifying the global options when selecting with C-c @ and then exporting. The subtree options for example: #+EXPORT_OPTIONS: H:2 num:t toc:f \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil #+EXPORT_FILE_NAME: tester are not used and just ignored. Shouldn't these overide the file settings from what I read in the org-manual. Where do these need to be placed. It is right below the subtree I am selecting for export. Cheers
Re: [O] new exporter drops :parameters ?
Hello, Charles Berry writes: > I am trying to put together a derived backend that makes use of Src Block > :parameters attribute. > > I can see that the header in a begin_src block is picked up by > > org-element-src-block-parser, as it should be when I try it interactively > > But not when I try > > M-: (org-export-to-buffer 'my-latex "*latex out*") RET > > I'd really like to have access to the header elements. > > AFAICS :parameters is nowhere to be found when using > org-export-to-buffer. This is because src blocks are executed before buffer is parsed. You can try to call `org-export-blocks-preprocess' on the following buffer (associated to a file): --8<---cut here---start->8--- #+name: bblock #+BEGIN_SRC R :exports code :et-cetera rnorm(2)+1 #+END_SRC --8<---cut here---end--->8--- and see what is really parsed: the removal happens on the Babel side. Depending on your needs, you may want to use ATTR_LATEX keyword instead. Regards, -- Nicolas Goaziou
Re: [O] Org-Export Subtree Options Not Working
Hello, Jeffrey Spencer writes: > When I input subtree options for modifying the global options when > selecting with C-c @ and then exporting. > > The subtree options for example: > > #+EXPORT_OPTIONS: H:2 num:t toc:f \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t > TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil > #+EXPORT_FILE_NAME: tester > > are not used and just ignored. Shouldn't these overide the file settings > from what I read in the org-manual. Where do these need to be placed. It is > right below the subtree I am selecting for export. You have to use headlines properties (with C-c C-x p) instead of keywords, i.e. --8<---cut here---start->8--- * Headline :PROPERTIES: :EXPORT_TITLE: subtree-title :END: Paragraph --8<---cut here---end--->8--- Regards, -- Nicolas Goaziou
Re: [O] Exporting to groff, now in org-export.el ...
Hello, Luis Anaya writes: > In terms of keywords, they all have to be revised, and many of them > are going to be removed. (Like long tables). I'll changed them from > tag=value to :blah value, right now they're not really meaningful for > groff and many of them stubbed. Ok. > I proposed to keep an eye on my github repository. I'll be working > on it and hopefully should be ready for prime time. I can't promise to keep an eye on the repository, but if you have any question (if possible with an example to illustrate it, as I don't know groff syntax), do not hesitate to ask. > (If I do not collapse of exhaustion taking care of them. :( ) There's the `sleep-for' function for that. Regards, -- Nicolas Goaziou
[O] Error evaluating dot code via variable
Hi,
If I have something like
,---
| #+name: dot-code
| #+begin_src perl :results output :cache no
| print < "Node\\nA"
| Core -> "Node\\nB"
| }
| END
|
| #+end_src
|
| #+header: :var input=dot-code
| #+header: :file tmp.pdf
| #+header: :cmdline -Kneato -Tpdf
| #+begin_src dot :exports both :cache yes
| $input
| #+end_src
`---
I get the following error when evaluating the second block:
,-
| executing Perl code block (dot-code)...
| "digraph G {
| overlap=false
| \"Node\\nA\"
| \"Node\\nB\"
| Core -> \"Node\\nA\"
| Core -> \"Node\\nB\"
| }
| "
| executing Dot code block...
| replace-regexp-in-string: Invalid use of `\' in replacement text
`-
If I paste the output of the first block into its own src block, like
this:
,
| #+header: :file tmp.pdf
| #+header: :cmdline -Kneato -Tpdf
| #+begin_src dot :exports both :cache no
| digraph G {
| overlap=false
| "Node\nA"
| "Node\nB"
| Core -> "Node\nA"
| Core -> "Node\nB"
| }
| #+end_src
`
I get no error on execution.
If I replace '\\n' with ' X ', i.e. something without '\', in the first
block, the error seen when using the variable $input does not occur.
I'm using Emacs 23.2.1 and Org 7.8.11. Is this a known issue?
Cheers
Loris
--
Loris Bennett
[O] latex (beamer) export and short title
Hi all,
I am having trouble to find a way to set a short title for the exported
beamer document.
Illustration:
I'd like to see
,
| \title[short title]{long title}
`
in the exported latex document.
The first shot
,
| #+TITLE: [short title]{long title}
`
was too easy, I guess.
Overriding org's setting of \title with
,
| #+TITLE: long title
| #+latex_header: \title[short title]{long title}
`
does not work either, as org's setting gets into the tex later.
What is the way to accomplish this?
Regards,
Andreas
[O] test suite failure
Just a heads-up: I just pulled, regenerated autoloads
(release_7.8.11-107-ga69f4b8),
and ran ``make check''. I got
,
| ...
| Ran 193 tests, 192 results as expected, 1 unexpected (2012-07-03
10:57:01-0400)
| 6 expected failures
|
| 1 unexpected results:
|FAILED test-ob-lob/call-with-header-arguments
`
The details of the failure (I haven't spent any time on it):
,
| "testing"
| Test test-ob-lob/call-with-header-arguments backtrace:
| replace-match(nil nil nil nil 3)
| (save-excursion (goto-char (match-beginning 3)) (replace-match hash
| org-babel-set-current-result-hash(nil)
| (prog1 (org-babel-execute-src-block nil (mkinfo (org-babel-process-p
| (if (and cache\? (equal new-hash old-hash)) (save-excursion (goto-ch
| (let* ((pre-params (org-babel-merge-params org-babel-default-header-
| (progn (fset (quote mkinfo) (function* (lambda (p) (block mkinfo (li
| (unwind-protect (progn (fset (quote mkinfo) (function* (lambda (p) (
| (let* ((--cl-letf-bound-- (fboundp (quote mkinfo))) (--cl-letf-save-
| (letf (((symbol-function (quote mkinfo)) (function* (lambda (p) (blo
| (letf* (((symbol-function (quote mkinfo)) (function* (lambda (p) (bl
| (flet ((mkinfo (p) (list "emacs-lisp" "results" p nil nil (nth 2 inf
| org-babel-lob-execute(("echo(input=\"testing\")" nil 0))
| (list "testing" (org-babel-lob-execute (org-babel-lob-get-info)))
| (let ((fn-1188 (function string=)) (args-1189 (list "testing" (org-b
| (should (string= "testing" (org-babel-lob-execute (org-babel-lob-get
| (save-restriction (move-beginning-of-line 1) (forward-line 6) (messa
| (progn (org-id-goto "fab7e291-fde6-45fc-bf6e-a485b8bca2f0") (setq to
| (unwind-protect (progn (org-id-goto "fab7e291-fde6-45fc-bf6e-a485b8b
| (let ((save-match-data-internal (match-data))) (unwind-protect (prog
| (save-match-data (org-id-goto "fab7e291-fde6-45fc-bf6e-a485b8bca2f0"
| (progn (save-match-data (org-id-goto "fab7e291-fde6-45fc-bf6e-a485b8
| (unwind-protect (progn (save-match-data (org-id-goto "fab7e291-fde6-
| (let ((wconfig (current-window-configuration))) (unwind-protect (pro
| (save-window-excursion (save-match-data (org-id-goto "fab7e291-fde6-
| (let* ((id-location (org-id-find "fab7e291-fde6-45fc-bf6e-a485b8bca2
| (org-test-at-id "fab7e291-fde6-45fc-bf6e-a485b8bca2f0" (move-beginni
| (lambda nil (org-test-at-id "fab7e291-fde6-45fc-bf6e-a485b8bca2f0" (
| byte-code("\306\307!q\210\310\216\311 \312\216\313\314\315\316\3
| ert--run-test-internal([cl-struct-ert--test-execution-info [cl-struc
| byte-code("\306\307!\211r\310\311!q\210\312 d\313\223)L\210\314\216
| ert-run-test([cl-struct-ert-test test-ob-lob/call-with-header-argume
| ert-run-or-rerun-test([cl-struct-ert--stats "\\(org\\|ob\\)" [[cl-st
| ert-run-tests("\\(org\\|ob\\)" #[(event-type &rest event-args) \30
| ert-run-tests-batch("\\(org\\|ob\\)")
| ert-run-tests-batch-and-exit("\\(org\\|ob\\)")
| (let ((org-id-track-globally t) (org-id-locations-file (convert-stan
| org-test-run-batch-tests()
| call-interactively(org-test-run-batch-tests nil nil)
| command-execute(org-test-run-batch-tests)
| command-line-1(("--eval" "(add-to-list 'load-path \"./lisp\")" "--ev
| command-line()
| normal-top-level()
| Test test-ob-lob/call-with-header-arguments condition:
| (wrong-type-argument stringp nil)
|FAILED 94/193 test-ob-lob/call-with-header-arguments
`
HTH,
Nick
Re: [O] how i pass output of one codeblock as iinput of another codeblock without manual copy paste
Thank you, Tom. It works like a charm! Now, I will read the document one more time very carefully and throughly. James On Mon, Jul 2, 2012 at 7:25 PM, Thomas S. Dye wrote: > James Kang writes: > > > Hi, > > > > I have been using code blocks with the following way to pass one's > > output to the other's input(or input variable). > > You can notice that I am manually copying/pasting the contents of > > "RESULTS" and create a table with a name "my_table". > > Now, is there anyway I can do this passing the output automatically > > without manual copy/paste? > > > > Thanks > > (using orgmode 7.8) > > > > #+srcname: code1 > > #+begin_src sh :exports code :results value table > > Some codes here > > #+end_src > > > > #+RESULTS: > > |Good results| > > #+tblname: my_table ### this is copied from the previous results > manually > > |Good results| > > #+call: transpose(table=my_table) > > > > #+results: transpose(table=my_table) > > |Good results Processed by transpose| > Aloha James, > > The Org mode manual should answer your question: > > http://orgmode.org/manual/var.html#var > > You'll probably want to use #+name: code1 rather than #+srcname: code1 > > Once you've done that, then #+call: transpose(table=code1) ought to > work, if the Library of Babel is loaded or you have otherwise defined > transpose. > > All the best, > Tom > > -- > Thomas S. Dye > http://www.tsdye.com >
[O] bug#11774: bug#11774: org-mode causes undo boundaries to be lost
On 03.07.2012 11:57, Toby Cubitt wrote: > On Mon, Jul 02, 2012 at 08:51:48AM +0200, Martin Pohlack wrote: >>> I'm still not entirely convinced that the boundary discarding logic in >>> org-self-insert-command is correct. For example, if I do the following: >>> >>> 1. Type some text at some location in an org-mode buffer >>> 2. Move to another location very far away >>>(without invoking any commands other than point motion) >>> 3. Type some more text >>> >>> then org-self-insert-cluster-for-undo collapses the undo changesets for >>> these two changes into one. Undoing then reverts both sets of changes at >>> once, even though those changes might be so far apart that they aren't >>> both visible at the same time in the buffer. >>> >>> That seems very undesirable to me. >> >> Having been involved in org-mode's collapsing code I am interested in >> this, but I cannot reproduce your problem. I used a very large org-mode >> file, inserted some text, moved down some pages and inserted some text >> again (3 chars each). Undoing was split between both parts, exactly as >> desired. Could you provide more details please? > > > Sure. The following steps produce the effect I described, at least for > me. This is on a fairly recent (a couple of weeks old) bzr build of > Emacs, and a similarly recent git build of org-mode: > > 1. $ emacs -Q > 2. C-x C-f test.org > 3. M-x org-mode [not really necessary since already in org-mode] > 5. C-u 50 M-x newline > 6. M-< > 7. type "a" > 8. M-> > 9. type "bc" > > buffer-undo-list now contains: > > (nil (52 . 54) (1 . 2) nil (1 . 51) (t . -1)) > > Note the lack of undo boundary between (52 . 54) and (1 . 2), which means > that undoing once (C-/) deletes both "bc" *and* "a" in one step. Understood. I tried exactly the same thing with an older emacs (GNU Emacs 23.2.1 (x86_64-pc-linux-gnu, GTK+ Version 2.24.4) of 2011-04-04 on crested, modified by Debian) and org-mode (6.33x and 7.6) and have this result: (nil (53 . 54) (52 . 53) nil (1 . 2) nil (1 . 51) (t 65535 . 65535)) Which is what one wants. Someone seems to be merging the self-insert commands in your situation. Probably the native merging code has changed in recent emacs itself. If this is confirmed, we could modify org-mode's merging code to only merge undo entries that span one character. Martin
[O] bug#11774: bug#11774: org-mode causes undo boundaries to be lost
On Mon, Jul 02, 2012 at 08:51:48AM +0200, Martin Pohlack wrote: > > I'm still not entirely convinced that the boundary discarding logic in > > org-self-insert-command is correct. For example, if I do the following: > > > > 1. Type some text at some location in an org-mode buffer > > 2. Move to another location very far away > >(without invoking any commands other than point motion) > > 3. Type some more text > > > > then org-self-insert-cluster-for-undo collapses the undo changesets for > > these two changes into one. Undoing then reverts both sets of changes at > > once, even though those changes might be so far apart that they aren't > > both visible at the same time in the buffer. > > > > That seems very undesirable to me. > > Having been involved in org-mode's collapsing code I am interested in > this, but I cannot reproduce your problem. I used a very large org-mode > file, inserted some text, moved down some pages and inserted some text > again (3 chars each). Undoing was split between both parts, exactly as > desired. Could you provide more details please? Sure. The following steps produce the effect I described, at least for me. This is on a fairly recent (a couple of weeks old) bzr build of Emacs, and a similarly recent git build of org-mode: 1. $ emacs -Q 2. C-x C-f test.org 3. M-x org-mode [not really necessary since already in org-mode] 5. C-u 50 M-x newline 6. M-< 7. type "a" 8. M-> 9. type "bc" buffer-undo-list now contains: (nil (52 . 54) (1 . 2) nil (1 . 51) (t . -1)) Note the lack of undo boundary between (52 . 54) and (1 . 2), which means that undoing once (C-/) deletes both "bc" *and* "a" in one step. HTH, Toby -- Dr T. S. Cubitt Mathematics and Quantum Information group Department of Mathematics Complutense University Madrid, Spain email: ts...@cantab.net web: www.dr-qubit.org
[O] my emacs hangs when using matplotlib with sessions
Dear all,
let say I have these lines:
#+PROPERTY: session *py*
#+PROPERTY: results output
#+BEGIN_SRC python
import matplotlib.pyplot as plt
a=[1,2,3]
#+END_SRC
I execute the code block, no problem
Then I execute this:
#+BEGIN_SRC python
plt.plot(a)
#+END_SRC
boom, emacs hangs
result doesn't change if I write plt.plot(a) directly in the *Python*
buffer activated by org-babel-pop-to-session.
if I use pylab (interactive mode of matplotlib), I can see a window with
the plot, but then the *Python* shell is unresponsive, and the only thing I
can do is just killing it.
Please note that
#+BEGIN_SRC python :session none
import matplotlib.pyplot as plt
a=[1,2,3]
plt.plot(a)
plt.savefig('dummy.png')
#+END_SRC
works perfectly.
It would be wonderful for me to be able to use sessions & matplotlib...
So, thanks a lot for any suggestions!
Giacomo M
Python 2.7.2 win32
matplotlib 1.1.0
Emacs 24.1.1 (i386-mingw-nt5.1.2600)
org-mode 7.8.11
[O] bug#11774: bug#11774: org-mode causes undo boundaries to be lost
> Which is what one wants. Someone seems to be merging the self-insert > commands in your situation. Probably the native merging code has > changed in recent Emacs itself. Indeed, self-insert-command used to be treated specially by the read-eval-loop and the merging was performed there. Now this command is handled like any other, and self-insert-command does the merging itself. In most cases the result is the same, but the behavior is not quite identical in the details. Stefan
[O] bug#11774: bug#11774: bug#11774: org-mode causes undo boundaries to be lost
On 7/3/12, Stefan Monnier wrote: > Indeed, self-insert-command used to be treated specially by the > read-eval-loop and the merging was performed there. Now this command is > handled like any other, and self-insert-command does the merging itself. > In most cases the result is the same, but the behavior is not quite > identical in the details. Here is the way I understand it: There are two problems with self-insert-command now, while before there was only one. The first is that it hardcodes the clustering by 20. As it happens, I strongly prefer clustering by 1. That is, I do not want undo to jump around or type more than necessary. I just want to autorepeat undo (C-/) until I get to where I need to be. Otherwise it is far too jerky and unpredictable and you have to type more either to delete (if you didn't undo far back enough) or add (if you undid too far). This was possible to work around before Emacs 24. You could advise self-insert-command or wrap it. This is why Org was able to control this with a variable to support clustering or not clustering. What is new in Emacs is that self-insert-command now destroys undo-boundary. If you wrap it, it destroys all of your effort on the next call to it. This causes subtle issues such as Org and undo-tree are dealing with. It is not reasonable to work around this because of the extra functionality you need to implement (especially if you want Org to do speed commands, table operations, and tag padding, which, who doesn't?). Unlike before, changing a hardcoded number or undo-boundary and then recompiling Emacs is necessary if you want to fix it. :( The loss of this ability to configure the cluster amount, and the subtle bug introduced, IMO merit a reversion or a fix to Emacs self-insert-command. Even just turning that magic 20 number into a variable would help. At least that's my understanding. I am just a user and I am not familiar with the internals. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
[O] bug#11774: bug#11774: org-mode causes undo boundaries to be lost
On 25.06.2012 13:35, Toby Cubitt wrote: > On Sun, Jun 24, 2012 at 11:52:41PM +0200, Toby Cubitt wrote: >> On Sun, Jun 24, 2012 at 11:39:08PM +0200, Bastien wrote: >>> Hi Toby, >>> >>> Toby Cubitt writes: >>> For some unknown reason, org-mode is causing the undo boundary between the (2 . 4) and (1 . 2) entries to be removed from `buffer-undo-list'. >>> >>> Can you try again with >>> >>> (setq org-self-insert-cluster-for-undo nil) >>> >>> and report? >> >> Yup, that fixes the problem. >> >> I don't fully understand the purpose of >> `org-self-insert-cluster-for-undo', given that the Emacs command loop >> already groups consecutive undo entries together, but presumably it >> enables a more aggressive form of clustering. Just to clarify this little piece here: I originally introduces this clustering code to mimic emacs' behavior in text mode. Org-mode's aggressive interception seemed to prevent that and undoing in org-mode felt unnatural compared to vanilla text mode. It was never meant to be *more* aggressive than emacs' original behavior. The grouping did not happen at the time. The original thread is here: http://lists.gnu.org/archive/html/emacs-orgmode/2009-02/msg00691.html Martin
[O] Bug in table export for latex? (underscore and ampersand)
I'm trying to export a table with the following cell:
BAT_30_CCR01_OUV_ZONE_PCE_30_2A_102_&_30_2A_101
The ampersand seems to be messing everything... I obtain this when I export:
BAT\_{}30\_{}CCR01\_{}OUV\_{}ZONE\_{}PCE\_{}30\_{}2A\_{}102_\&_30\_{}2A\_{}101
For this to export normally, I would expect this:
BAT\_{}30\_{}CCR01\_{}OUV\_{}ZONE\_{}PCE\_{}30\_{}2A\_{}102\_{}\&\_{}30\_{}2A\_{}101
Here is the difference:
102_\&_30
102\_{}\&\_{}30
The underscore isn't escaped, which results in an unwanted subscript in the
exported table.
Is this a bug?
Any quick fix?
Thanks in advance!
[O] bug#11774: bug#11774: bug#11774: org-mode causes undo boundaries to be lost
> The first is that it hardcodes the clustering by 20. I guess that's the problem which is not new. > This was possible to work around before Emacs 24. You could advise > self-insert-command or wrap it. This is why Org was able to control > this with a variable to support clustering or not clustering. IIUC Org's clustering was only introduced because self-insert-command's clustering only worked when it was handled by the read-eval-loop, so it was not done to "avoid" the clustering, but to make it work in more cases. So it might be unneeded in Emacs-24. > What is new in Emacs is that self-insert-command now destroys > undo-boundary. If you wrap it, it destroys all of your effort on the > next call to it. I don't have it fresh in my memory but if you can post some sample code showing what you're doing, and how self-insert-command's behavior makes it difficult, maybe we can make it work better. > self-insert-command. Even just turning that magic 20 number into a > variable would help. Providing it as a variable would be very easy, indeed. Stefan
[O] syntax highlighting of inline LaTeX fragments
dear org-moders,
is it possible to syntax-highlight inline LaTeX fragments,
such as $V$ or \cite{smith2012generating} ?
I know you can highlight LaTeX code blocks, but I'm looking specifically
for highlighting of inline fragments.
thanks for help,
ilya
[O] bug#11774: bug#11774: bug#11774: org-mode causes undo boundaries to be lost
On 7/3/12, Stefan Monnier wrote: >> self-insert-command. Even just turning that magic 20 number into a >> variable would help. > > Providing it as a variable would be very easy, indeed. Hi Stefan, To clarify, that is actually the only thing that I need as a user for self-insert-command. It would make an enormous difference in my use of Emacs. Huge. So I don't need undo-boundary to work in any particular way -- IF I have the ability to cluster self-insert-command by 1 instead of that hardcoded 20 throughout Emacs (including Org of course). My need for undo-boundary to work the way it did before is only so that I could call undo-boundary after every invocation of self-insert-command. Therefore, IF we have that variable, then undo-boundary considerations should be simply to DTRT for undo-tree, org-self-insert-command, and other code, in such a way that subtle bugs are prevented. Maybe the user should be able to set undo boundaries and have them work after self-insert-command? Dunno, I'm not familiar with internals enough to opine. Hope that clarifies. I will follow the discussion as long as I'm CC'ed as I am now. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
[O] bug#11774: bug#11774: bug#11774: bug#11774: org-mode causes undo boundaries to be lost
On 7/3/12, Samuel Wales wrote: > My need for undo-boundary to work the way it did That should read, "My need for self-insert-command to work the way it did".
Re: [O] [ANN] Beamer back-end for org-export in contrib/
Hello Nicolas,
On Mon, Jul 2, 2012 at 2:22 PM, Nicolas Goaziou wrote:
>
> This should be possible with `org-e-beamer-environments-extra', i.e.
>
> (add-to-list 'org-e-beamer-environments-extra
>'("onlyenv" "O" "\\begin{onlyenv}%a" "\\end{onlyenv}"))
>
> Then you set headline's BEAMER_env property to onlyenv and modify
> BEAMER_act accordingly.
>
Thanks! This works very well. :)
>>> Every plain list has support for `:overlay' attribute (through
>>> ATTR_BEAMER affiliated keyword). Also, ordered (resp. description)
>>> lists make use of `:template' (resp. `:long-text') attribute.
>>>
>>
>> I wasn't clear what you meant here. Could you give an example? Did you
>> mean I can specify overlay specification for list items with the above
>> mechanism? I'm not clear on the syntax here.
>
> These attributes modify the whole list. To set overlays for individual
> items, use export snippets. Examples follow:
>
> #+ATTR_BEAMER: :template "i)" :overlay "<+->"
Again this works beautifully!
>> I have another feature request (for the distant future) with regards to
>> lists; I would like to put tikz nodes in list items. I have tried that
>> in the past with very limited success. For an example, you can look
>> here:
>>
>>
[O] org-agenda-done face should override individual elements
In agenda log mode, the org-agenda-done face is excellent. However, todo keywords and priorities are still faceified specially like they are in the agenda. Perhaps org-agenda-done face should be applied later, so that the entire line is green by default. I get distracted by the repeat-to todo keyword, because the color falsely says "I need to be done" when it should say "don't pay attention to me (unless I need to be done)". Applying org-agenda-done face later solves this. Thanks. Samuel -- The Kafka Pandemic: http://thekafkapandemic.blogspot.com
Re: [O] Org-Export Subtree Options Not Working
Thanks, that fixed it but another question. if you export the whole file then and not just the selection can you use a tag or property to specify a different directory to export into instead of the same directory as the org file. Will creating the Property Tag at the top level work for this?? Also, is there an easy way to tell it to ignore the first say 2 headers in the file and only export starting with the third header. My first two headers are just to keep track of dates eg. * 2010 ** June I would rather these be ignored when doing the export. The only way I know is to export the subtree. If there isn't then is there a way to write a command that would take the current place your working in go up to the third level heading, select the third level, and run an export command. Or the fastest way to do this via key bindings? Cheers, Jeff On Tue, Jul 3, 2012 at 7:29 PM, Nicolas Goaziou wrote: > Hello, > > Jeffrey Spencer writes: > > > When I input subtree options for modifying the global options when > > selecting with C-c @ and then exporting. > > > > The subtree options for example: > > > > #+EXPORT_OPTIONS: H:2 num:t toc:f \n:nil @:t ::t |:t ^:t -:t f:t *:t <:t > > TeX:t LaTeX:t skip:nil d:nil todo:t pri:nil tags:nil > > #+EXPORT_FILE_NAME: tester > > > > are not used and just ignored. Shouldn't these overide the file settings > > from what I read in the org-manual. Where do these need to be placed. It > is > > right below the subtree I am selecting for export. > > You have to use headlines properties (with C-c C-x p) instead of > keywords, i.e. > > --8<---cut here---start->8--- > * Headline > :PROPERTIES: > :EXPORT_TITLE: subtree-title > :END: > Paragraph > --8<---cut here---end--->8--- > > > Regards, > > -- > Nicolas Goaziou >
Re: [O] syntax highlighting of inline LaTeX fragments
Also interested in if this is possible and what do you use to highlight
LaTeX code blocks.
On Wed, Jul 4, 2012 at 9:11 AM, Ilya Shlyakhter wrote:
> dear org-moders,
> is it possible to syntax-highlight inline LaTeX fragments,
> such as $V$ or \cite{smith2012generating} ?
> I know you can highlight LaTeX code blocks, but I'm looking specifically
> for highlighting of inline fragments.
> thanks for help,
> ilya
>
>
>
>
[O] [babel] export of table with inline source blocks
Hi all,
I am having problems with the export of a minimal org file:
,
| #+PROPERTY: session *R*
|
| * Test
|
| | dtrn | xgnd |
| |--+---|
| | engd | src_R[:exports results :results raw replace]{1/2} |
| | engd | src_R[:exports results :results raw replace]{1/2} |
| | engd | src_R[:exports results :results raw replace]{1/2} |
|
`
Problems:
1. only the first inline code is executed
2. the inline block is not replaced
This is the latex output:
,
| \begin{center}
| \begin{tabular}{ll}
| dtrn & xgnd\\
| \hline
| engd & src$_{\mathrm{R[}}$:exports results :results raw replace]\{1/2\} 0.5\\
| engd & src$_{\mathrm{R[}}$:exports results :results raw replace]\{1/2\}\\
| engd & src$_{\mathrm{R[}}$:exports results :results raw replace]\{1/2\}\\
| \end{tabular}
| \end{center}
`
Are inline blocks not allowed in tables?
Regards,
Andreas
