From: "François Pinard" <email@example.com>
Subject: Re: Display/print text only for export
Date: Sat, 05 May 2012 18:19:12 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Bastien's message of "Tue, 01 May 2012 16:22:16 +0200")
Bastien <firstname.lastname@example.org> writes:
> Does #+INCLUDE: suits your needs?
Oh! I never used a colon after #+INCLUDE. Checking the Org manual, the
colon is systematically there, except within the last paragraph of node
/Updating files/. Maybe it could be added for consistency?
I did not notice my error as everything worked without the colon.
Adding it everywhere in my files, things still works. Should Org be
more strict about this? I would have corrected myself earlier...
next prev parent reply other threads:[~2012-05-05 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-24 21:52 Display/print text only for export Andreas Kalex
2012-05-01 14:22 ` Bastien
2012-05-05 22:19 ` François Pinard [this message]
2012-05-05 22:55 ` Bastien
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 \
* 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).