From: Thorsten Jolitz <tjolitz@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: New Exporter BUG/Change in behaviour
Date: Sat, 06 Apr 2013 23:50:22 +0200 [thread overview]
Message-ID: <87d2u7wcpt.fsf@gmail.com> (raw)
In-Reply-To: 87hajkx1rv.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
Hello,
> The new exporter distinguishes between subtree export (toggled with C-s
> key within the dispatcher) and region export. In the old exporter, C-c @
> + export command would give you a subtree export. This is not the case
> in the new exporter. You have to explicitly mention you want a subtree
> export. On the other hand, you don't need to select a region beforehand.
> In other words, you don't trigger a subtree export anymore with C-c @
> (but it triggers a region export).
>
> If you export a subtree in the new exporter jargon, you can override
> locally #+options: line by setting top headline's :EXPORT_OPTIONS:
> property to an appropriate value, e. g. :EXPORT_OPTIONS: tasks:t.
Shouldn't the
,---------------------
| :EXPORT_OPTIONS: d:t
`---------------------
setting in the following minimal org-file export the property-drawer for
this subtree too?
,-----------------------
| * header1
| :PROPERTIES:
| :EXPORT_OPTIONS: d:t
| :END:
|
| hello world
|
| |hello| table|
|
`-----------------------
Exporting to an ASCII buffer:
,------------
| C-c C-e t A
`------------
gives
,------------------
| Thorsten Jolitz
|
|
| Table of Contents
| _________________
|
| 1 header1
|
|
| 1 header1
| =========
|
| hello world
|
| hello| table|
`------------------
--
cheers,
Thorsten
next prev parent reply other threads:[~2013-04-06 21:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-04-05 16:52 New Exporter BUG/Change in behaviour Bernt Hansen
2013-04-05 18:36 ` Nicolas Goaziou
2013-04-05 19:04 ` Bernt Hansen
2013-04-06 21:50 ` Thorsten Jolitz [this message]
2013-04-06 22:22 ` Nicolas Goaziou
2013-04-06 22:47 ` Thorsten Jolitz
2013-04-06 23:07 ` Nicolas Goaziou
2013-04-06 23:27 ` Thorsten Jolitz
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87d2u7wcpt.fsf@gmail.com \
--to=tjolitz@gmail.com \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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).