From: Rick Frankel <firstname.lastname@example.org> To: email@example.com Subject: Re: Bug (?) in new exporter (export subtree) Date: Thu, 17 Jan 2013 08:28:49 -0500 [thread overview] Message-ID: <20130117132849.GA39115@BigDog.local> (raw) In-Reply-To: <firstname.lastname@example.org> On Wed, Jan 16, 2013 at 07:36:10PM +0100, Nicolas Goaziou wrote: > Rick Frankel <email@example.com> writes: > > > 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. > > It doesn't, AFAIU. Could you explain how you do export (in particular, > where is the point when you call the export subtree process) and what do > you expect on a simple example ? > > For me: > > #+begin_src org > #+TITLE: title > #+OPTIONS: toc:t > * Level 1 > Body 1 X > ** Level 2 > Body 2 > *** Level 3 > Body 3 > #+end_src > > with point at X will have "Level 1" as its title, but "Level 1" will > appear neither in the table of contents nor as the first section of the > produced document. So, it seems that as long as there is a body (or blank) line after the parent heading and you position the cursor on that line, it works (point at X): #+begin_src org * Title X ** heading 1 text ** heading 2 ... #+end_src But if there is no blank line after the "title", there is no way to get the expected results with the point either on the title line or the first asterix on heading 1: #+begin_src org * Title ** heading 1 text ** heading 2 ... #+end_src rick
next prev parent reply other threads:[~2013-01-17 13:28 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2013-01-15 20:36 Rick Frankel 2013-01-16 18:36 ` Nicolas Goaziou 2013-01-17 13:28 ` Rick Frankel [this message] 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: 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=20130117132849.GA39115@BigDog.local \ --firstname.lastname@example.org \ --email@example.com \ --subject='Re: Bug (?) in new exporter (export subtree)' \ /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 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).