Re: [O] prevent auto appending #+INCLUDE files title

[Manuel Koell]

Hello Rasmus,

I think you got me wrong or I don't understand correctly ^^

The problem is, when I export a file which uses #+INCLUDE inside, for example my index.org where I want to include the latest 5 posts (generated from sitemap.org). The exported index.html has the wrong title/h1 then: <title>My title Sitemap</title>. The files I used to include append their title to the index.org document then. This is not something I would expect if I already set the #+TITLE option. Idk if this is a bug or a feature. Do you've any workaround? I dont know why orgmode is mess up my title.

2015-11-23 18:13 GMT+01:00 Rasmus <address@hidden>:

Hi Manuel,

Manuel Koell <address@hidden> writes:

> I tried to use #+INCLUDE "sitemap.org" :only-contents t with the
> :auto-sitemap option on my publishing project, but whenever I include a
> file this way the title appends to the exported document title.
>
> example file (test.org)
>
> ```
>
> #+TITLE: My title
>
> #+INCLUDE "sitemap.org" :only-contents t
> ```
>
> Now the exported document title test.html contains the title: My title
> Sitemap
> Expected behaviour: the title I set with #+TITLE

Currently :only-contents is just referring to a headline or so.  E.g.

          #+include: "test.org::#head1" :only-contents t

will limit the input to the sense of contents as understood by
org-element.

I agree that it might extend the meaning of :only-contents to also work on
full files, though it’s not clear what the proper behavior is.  In
particular, what keywords would it extend to?  E.g. what about
#+backend_header lines, e.g. #+html_header?  To me, this sounds like a
difficult problem to get right...

An easy fix in your problem in this case is probably :lines "2-".

Rasmus

--
I feel emotional landscapes they puzzle me