emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rick Frankel <rick@rickster.com>
To: emacs-orgmode@gnu.org
Subject: Bug (?) in new exporter (export subtree)
Date: Tue, 15 Jan 2013 15:36:29 -0500	[thread overview]
Message-ID: <20130115203629.GA25867@BigDog.local> (raw)

In the new exporter, when the option to export only the subtree is
specified, the first heading in the subtree is used as the title of
the document. This seems wrong, as it becomes the title, the first
element in the table of contents and the first (not necessarily
the top level) section in the document.

When the document is explicitly narrowed to the subtree, or the
subtree is the selected region, the #+Title: attribute is used for the
document title, which seems to be better.

Arguably, using the subtree heading for the title would be the most
logical solution when exporting a subtree -- in my case that would
usually DWIM.


             reply	other threads:[~2013-01-15 20:36 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-01-15 20:36 Rick Frankel [this message]
2013-01-16 18:36 ` Bug (?) in new exporter (export subtree) Nicolas Goaziou
2013-01-17 13:28   ` Rick Frankel
2013-01-18 21:12     ` Nicolas Goaziou

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:

  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=20130115203629.GA25867@BigDog.local \
    --to=rick@rickster.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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