From: Nick Dokos <firstname.lastname@example.org>
To: Henry Hirsch <email@example.com>
Cc: firstname.lastname@example.org, Emacsemail@example.com
Subject: Re: Include does not work when doing org-export-as-org
Date: Tue, 11 Oct 2011 10:27:56 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: Message from Nick Dokos <email@example.com> of "Tue, 11 Oct 2011 10:21:28 EDT." <firstname.lastname@example.org>
Nick Dokos <email@example.com> wrote:
> Nick Dokos <firstname.lastname@example.org> wrote:
> > Henry Hirsch <email@example.com> wrote:
> > > Hello everyone,
> > >
> > > I am trying to export an org-file with includes.
> > > When I export as PDF all includes work but when
> > > I export as org-file the includes are getting ignored.
> > >
> > What does "export as org-file" mean? What do you do exactly?
> Never mind: I didn't read the subject line.
C-h f org-export-as-org says:
| org-export-as-org is an interactive Lisp function in `org-exp.el'.
| (org-export-as-org ARG &optional HIDDEN EXT-PLIST TO-BUFFER BODY-ONLY
| Make a copy with not-exporting stuff removed.
| The purpose of this function is to provide a way to export the source
| Org file of a webpage in Org format, but with sensitive and/or irrelevant
| stuff removed. This command will remove the following:
| - archived trees (if the variable `org-export-with-archived-trees' is nil)
| - comment blocks and trees starting with the COMMENT keyword
| - only trees that are consistent with `org-export-select-tags'
| and `org-export-exclude-tags'.
It is not a general purpose exporter. It is supposed to allow you to post
org examples on web pages. I presume it is used when exporting to Worg.
In particular, I assume it does not process includes, because they need
to be preserved in examples.
next prev parent reply other threads:[~2011-10-11 14:28 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-11 12:38 Henry Hirsch
2011-10-11 13:41 ` Nick Dokos
2011-10-11 13:53 ` Henry Hirsch
2011-10-11 14:01 ` Henry Hirsch
2011-10-11 14:09 ` Nick Dokos
2011-10-11 14:18 ` Nick Dokos
2011-10-11 14:21 ` Nick Dokos
2011-10-11 14:27 ` Nick Dokos [this message]
2011-10-11 14:34 ` Henry Hirsch
[not found] ` <firstname.lastname@example.org>
2011-10-11 14:57 ` Nick Dokos
2011-10-11 15:09 ` Henry Hirsch
2011-10-11 15:37 ` Nick Dokos
2011-10-11 16:09 ` Henry Hirsch
2011-10-11 16:51 ` Nick Dokos
2011-10-12 7:44 ` Henry Hirsch
2011-10-12 10:15 ` Carsten Dominik
2011-10-21 16:49 ` Bastien
2011-10-21 17:14 ` Nick Dokos
2011-10-11 18:27 ` Carsten Dominik
2011-10-11 14:22 ` Henry Hirsch
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).