Hi Richard,
>
> I think what you want to do is put the EXPORT_LATEX_CLASS_OPTIONS (and
> the TITLE) as a property in the property drawer, like this:
>
> * Projektboard :noexport:
> :PROPERTIES:
> :EXPORT_LATEX_CLASS_OPTIONS: [landscape]
> :EXPO
Hi Axel,
Axel Kielhorn writes:
> I want to export a subtree with a columnview dynamic block in
> landscape orientation. I don’t want just a rotated table, the whole
> page should be in landscape mode. I may have to tweak the page layout
> using geometry as well, thus I probably need EXPORT_LAT
Hi,
I want to export a subtree with a columnview dynamic block in landscape
orientation.
I don’t want just a rotated table, the whole page should be in landscape mode.
I may have to tweak the page layout using geometry as well,
thus I probably need EXPORT_LATEX_HEADER.
I’m using:
Org-mode versio
John Hendy wrote:
> Thinking about it more, using select_tags as a potential solution to
> your export of a subtree without navigating to it, problems could
> arise if more than one were tagged. If multiple same-level headlines
> were tagged with the select_tag, which one should Org use as the
> "m
On Thu, Dec 10, 2015 at 8:50 PM, Skip Collins wrote:
> Herbert Sitz wrote:
>> * Main tree :myexporttree:
>> fkjaldfk
>> ** subhead
>> ** subhead
>> * anoher heading 1
>> * another heading level 1
>> ** subhead
>> ** subhead
>
> I did try using the default SELECT_TAG :export: on my main docume
Herbert Sitz wrote:
> * Main tree :myexporttree:
> fkjaldfk
> ** subhead
> ** subhead
> * anoher heading 1
> * another heading level 1
> ** subhead
> ** subhead
I did try using the default SELECT_TAG :export: on my main document
subtree. The problem is that the subtree is not "promoted" to th
On Thu, Dec 10, 2015 at 6:27 PM, Herbert Sitz wrote:
> Not a perfect solution, buy I think you can use the #+SELECT_TAGS option to
> set which tress will be exported by default, then tag your desired export
> tree with that tag. Then when you export the full buffer (not just a
> subtree) it will
Not a perfect solution, buy I think you can use the #+SELECT_TAGS option to
set which tress will be exported by default, then tag your desired export
tree with that tag. Then when you export the full buffer (not just a
subtree) it will choose the tree with that tag.
E.g.,
Andreas Leha wrote:
> Skip Collins writes:
>>> Try to run `org-export-dispatch' with a prefix from the second time
>>> onwards (so, do C-u C-c C-e).
>>
>> Good try, but it does not do what I want. It selects the subtree
>> currently at point, just as if I ran the dispatcher again and selected
>>
Hi Skip,
Skip Collins writes:
> Andreas Leha wrote:
>>> The export dispatcher allows me to export only the current subtree.
>>> This is nice, but I would like to avoid having to put point in just
>>> the right place before invoking the dispatcher. I have a document with
>>> lots of things in it.
Andreas Leha wrote:
>> The export dispatcher allows me to export only the current subtree.
>> This is nice, but I would like to avoid having to put point in just
>> the right place before invoking the dispatcher. I have a document with
>> lots of things in it. One of the top-level headlines contai
Hi Skip,
Skip Collins writes:
> The export dispatcher allows me to export only the current subtree.
> This is nice, but I would like to avoid having to put point in just
> the right place before invoking the dispatcher. I have a document with
> lots of things in it. One of the top-level headlines
The export dispatcher allows me to export only the current subtree.
This is nice, but I would like to avoid having to put point in just
the right place before invoking the dispatcher. I have a document with
lots of things in it. One of the top-level headlines contains the
content of what I want to
Xebar Saram writes:
> Hi
>
> i was wondering if anyone knows how to export a subtree as a simple org file.
> i know i can copy paste into a new file but it seems quick to just export a
> subtree to a new org file :)
>
Narrow to subtree (C-x n s) then export to org (C-c C-e o o).
Xebar Saram writes:
> Hi
>
> i was wondering if anyone knows how to export a subtree as a simple org file.
> i know i can copy paste
> into a new file but it seems quick to just export a subtree to a new org file
> :)
>
Can you use the org backend of the exporter?
C-c C-e C-s O o
perhaps?
N
Hi
i was wondering if anyone knows how to export a subtree as a simple org
file. i know i can copy paste into a new file but it seems quick to just
export a subtree to a new org file :)
best
z
On 2015-02-07 19:55, John Kitchin writes:
> For a different approach, you could make this kind of an emacs script. I
> have not done this too often, and it can be tricky to setup and debug.
Very interesting! Thank you for the suggestion.
Alan
--
OpenPGP Key ID : 040D0A3B4ED2E5C7
signature.a
For a different approach, you could make this kind of an emacs script. I
have not done this too often, and it can be tricky to setup and debug.
#+BEGIN_SRC emacs-lisp :tangle export-org-section :shebang #!/bin/sh
:;exec emacs -batch -l ~/Dropbox/kitchingroup/jmax/init.el -l "$0" "$@"
;; usage: e
On 2015-02-05 08:27, "Charles C. Berry" writes:
> On Thu, 5 Feb 2015, Alan Schmitt wrote:
>
>> Hello,
>>
>> I'm teaching a class where I have a big monolithic file for all the
>> lectures. Right now I export each lecture as a subtree from the file
>> itself, but I would like to do it from a Makef
On Thu, 5 Feb 2015, Alan Schmitt wrote:
Hello,
I'm teaching a class where I have a big monolithic file for all the
lectures. Right now I export each lecture as a subtree from the file
itself, but I would like to do it from a Makefile. Is it possible to
export a subtree from the command line? if
Hello,
I'm teaching a class where I have a big monolithic file for all the
lectures. Right now I export each lecture as a subtree from the file
itself, but I would like to do it from a Makefile. Is it possible to
export a subtree from the command line? if so, how do I specify the
subtree that I wa
Hi Edward,
these properties come only into effect is the export is restricted to the
subtree carrying these properties.
HTH
- Carsten
On 28.7.2013, at 01:49, Edward DeMeulle wrote:
> It appears that I'm using the properties syntax correctly, however I
> cannot seem to get export to use the o
It appears that I'm using the properties syntax correctly, however I
cannot seem to get export to use the options I set in the properties
drawer. If I move the LaTeX_CLASS and OPTIONS over to their #+
equivalents at the top of the file they work just fine. Is there
something (hopefully not *too* ob
I want to use particular LaTeX headers when I export a subtree. Is there a
way to do this? (EXPORT_TEXT is close, but I need stuff in the LaTeX
preamble, not in the document itself.)
--Colin
24 matches
Mail list logo
