From: Carsten Dominik <carsten.dominik@gmail.com>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org, Bob Kline <bkline@rksystems.com>
Subject: Re: Included org-mode files not exported properly
Date: Sat, 8 Aug 2009 06:15:27 +0200 [thread overview]
Message-ID: <3A493506-CAED-4958-B6C1-B56BE247D716@gmail.com> (raw)
In-Reply-To: <25106.1249686238@gamaville.dokosmarshall.org>
Hi Nick,
you are completely right, thanks for diffing.
The documentation describes how things *should* work, i.e.
#+include file.org
without any markup argument should include and process the file
contents normally, while
#+include file.org src org
Should include the file as an source code example. In this case,
lines that look like headlines and commends should be "quoted" by
preceding them with a comma, so make sure they are not mistaken
for headlines or meta lines.
I believe this now works correctly again, please verify.
- Carsten
On Aug 8, 2009, at 1:03 AM, Nick Dokos wrote:
> Bob Kline <bkline@rksystems.com> wrote:
>
>> At Fri, 7 Aug 2009 16:32:15 +0200,
>> Carsten Dominik wrote:
>>
>>> this bug was fixed on July 24:
>>>
>>> http://repo.or.cz/w/org-mode.git?a=commitdiff;h=68b65e8f480c17cfe1024001c236eb4065893f4d
>>>
>>> so you probably need to upgrade.
>>
>> Hmm. I pulled down the latest code directly from the git repo, and
>> I'm
>> still seeing the buggy behavior. Did you have a different meaning in
>> mind for "upgrade"?
>>
>
> I suggested a workaround to Bob (unfortunately, I forgot to copy the
> list
> so it's in a different thread): use
>
> #+INCLUDE: "foo" markup
>
> but I think Bob is right that there is a problem (possibly more than
> one).
>
> o First, this does not agree with the documentation. In fact, Michael
> Zeller had proposed a change in the documentation (see
> http://thread.gmane.org/gmane.emacs.orgmode/15924) to make it
> conform to
> the current working of the code. Carsten, could you take a look and if
> you agree, apply that patch? (but see below first).
>
> o Second, the markup argument can be anything. If it is present, then
> the included file is processed as an org mode file for export (unless
> markup is "src" or "SRC", in which case the lang argument comes into
> the
> picture). In the thread above, Michael Zeller suggests "org" as the
> value
> of the markup and his documentation fix is phrased accordingly, but as
> far as the code goes that's purely conventional.
>
> o Third, if the markup argument is not present, then org-get-file-
> contents
> returns the contents of the file as a strings with commas preceding
> the headlines, as Bob mentioned. What's this all about?
>
> Thanks,
> Nick
>
next prev parent reply other threads:[~2009-08-08 4:16 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-08-07 1:41 Included org-mode files not exported properly Bob Kline
2009-08-07 14:32 ` Carsten Dominik
2009-08-07 15:13 ` Bob Kline
2009-08-07 23:03 ` Nick Dokos
2009-08-08 4:15 ` Carsten Dominik [this message]
2009-08-08 14:23 ` Bob Kline
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=3A493506-CAED-4958-B6C1-B56BE247D716@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bkline@rksystems.com \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.com \
/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).