emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Bernt Hansen <bernt@norang.ca>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: New Exporter BUG/Change in behaviour
Date: Fri, 05 Apr 2013 15:04:00 -0400	[thread overview]
Message-ID: <87li8wyf33.fsf@norang.ca> (raw)
In-Reply-To: <87hajkx1rv.fsf@gmail.com> (Nicolas Goaziou's message of "Fri, 05 Apr 2013 20:36:52 +0200")

Nicolas Goaziou <n.goaziou@gmail.com> writes:

> Hello,
>
> Bernt Hansen <bernt@norang.ca> writes:
>
>> Is this a bug?
>
> No, it isn't.
>
>> My current workaround is to delete the global #+OPTIONS
>> line (but that doesn't feel right since I have to add it back to export
>> what is left to do for the entire file when sharing it with others).  I
>> regularly export small subtrees (with C-c @) to copy ASCII / HTML export
>> results to emails so the old exporter behaviour was much more
>> predictable in the results I would get when using C-c @.
>
> 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.

Thanks for the clarification!  I'll give it a whirl :)

Regards,
Bernt

next prev parent reply	other threads:[~2013-04-05 19:04 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 [this message]
2013-04-06 21:50   ` Thorsten Jolitz
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=87li8wyf33.fsf@norang.ca \
    --to=bernt@norang.ca \
    --cc=emacs-orgmode@gnu.org \
    --cc=n.goaziou@gmail.com \
    /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

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).