From: Nick Dokos <email@example.com>
Subject: Re: Include does not work when doing org-export-as-org
Date: Tue, 11 Oct 2011 10:57:58 -0400 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: Message from Henry Hirsch <email@example.com> of "Tue, 11 Oct 2011 16:34:14 +0200." <20111011143414.GA25699@olymp.office.virtualminds.de>
Henry Hirsch <firstname.lastname@example.org> wrote:
> On Tue, Oct 11, 2011 at 10:27:56AM -0400, Nick Dokos wrote:
> > In particular, I assume it does not process includes, because they need
> > to be preserved in examples.
> > Nick
> So do you think it is reasonable that org-export-as-org is the only mode
> of export which is exhibiting a different behaviour?
It's certainly reasonable: it does not pretend to be a general-purpose
exporter. It may be misnamed though: if org-export-as-org is only used
in batch processing of e.g. Worg, then it can be renamed to something more
obscure and made non-interactive, so that it would not confuse the unwary.
One could imagine a general-purpose org-export-as-org that processes
includes, but I'm not sure what else it would do: just copy it's input
to its output mostly - other than processing includes, is there anything
else that it should do?
> For my part I think it is not. I used to love org-mode above
> everything. But this just leaves me not amused.
Well, there are a couple of options:
o org is very much a scratch-your-itch project - so you can
certainly go ahead and implement what you want.
o explain your use case: if it is compelling enough, somebody
might be motivated to implement what you ask for (but you need
to specify it exactly - and if somebody else implements it, be
prepared to compromise...)
But it is certainly *not* the case that org is some ivory tower project
that exists for theoretical purity only: there are hacks, work-arounds,
inconsistencies and bugs.
next prev parent reply other threads:[~2011-10-11 14:58 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
2011-10-11 14:34 ` Henry Hirsch
[not found] ` <email@example.com>
2011-10-11 14:57 ` Nick Dokos [this message]
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).