Bug (?) in new exporter (export subtree)

Bug (?) in new exporter (export subtree)

[Rick Frankel]

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.

rick

Re: Bug (?) in new exporter (export subtree)

[Nicolas Goaziou]

Hello,

Rick Frankel <rick@rickster.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.


Regards,

-- 
Nicolas Goaziou

Re: Bug (?) in new exporter (export subtree)

[Rick Frankel]

On Wed, Jan 16, 2013 at 07:36:10PM +0100, Nicolas Goaziou wrote:
> Rick Frankel <rick@rickster.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

Re: Bug (?) in new exporter (export subtree)

[Nicolas Goaziou]

Rick Frankel <rick@rickster.com> writes:

> 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

Indeed, you have to be within the subtree you want to export in order to
effectively export it. In your example there's no such place, so there's
no way to tell which subtree you want to be exported.

This is a reasonable behaviour in my opinion.


Regards,

-- 
Nicolas Goaziou