emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Manuel Koell <man.koell@gmail.com>
To: Rasmus <rasmus@gmx.us>
Cc: org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: prevent auto appending #+INCLUDE files title
Date: Mon, 23 Nov 2015 18:28:08 +0100	[thread overview]
Message-ID: <CAAAbm0r9W2mMrE0XkK6LEuc7orUOi88-WsprQ+fSoiCAxZ=8zQ@mail.gmail.com> (raw)
In-Reply-To: <87bnak1vwu.fsf@gmx.us>

[-- Attachment #1: Type: text/plain, Size: 1921 bytes --]

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 <rasmus@gmx.us>:

> Hi Manuel,
>
> Manuel Koell <man.koell@gmail.com> 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
>
>
>

[-- Attachment #2: Type: text/html, Size: 2868 bytes --]

  reply	other threads:[~2015-11-23 17:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-23 14:57 prevent auto appending #+INCLUDE files title Manuel Koell
2015-11-23 17:13 ` Rasmus
2015-11-23 17:28   ` Manuel Koell [this message]
2015-11-23 17:33     ` Rasmus
2015-11-23 18:28       ` Manuel Koell

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='CAAAbm0r9W2mMrE0XkK6LEuc7orUOi88-WsprQ+fSoiCAxZ=8zQ@mail.gmail.com' \
    --to=man.koell@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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
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

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