From: Nick Dokos <email@example.com>
To: Henry Hirsch <firstname.lastname@example.org>
Cc: email@example.com, firstname.lastname@example.org
Subject: Re: Include does not work when doing org-export-as-org
Date: Tue, 11 Oct 2011 11:37:54 -0400 [thread overview]
Message-ID: <email@example.com> (raw)
In-Reply-To: Your message of "Tue, 11 Oct 2011 17:09:01 +0200." <20111011150901.GB25699@olymp.office.virtualminds.de>
Henry Hirsch <firstname.lastname@example.org> wrote:
> On Tue, Oct 11, 2011 at 10:57:58AM -0400, Nick Dokos wrote:
> > o org is very much a scratch-your-itch project - so you can
> > certainly go ahead and implement what you want.
> I get it. If I want something fixed I gotta do it myself.
> Have a nice day, and thank you for sobering me up.
I'm sorry I offended you: that was not my intention at all.
But the above is certainly a misrepresentation of what I said.
Let me repeat:
... 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...)
A lot of people do follow the first way - many follow the second.
You are certainly free to propose some other way to proceed.
So far what you have done is identified it a behavior that does not
meet your expectations. It may be considered a bug or it may be not.
If the "bug" is fixed, it would break an existing use case (exporting
org example to web pages), which was in fact the primary reason for
providing the interface (somebody scratched that itch). So why should
it be changed (or more likely: why should another interface be added)
to meet your expectations? What is *your* use case? That is not at
all clear, so far at least.
next prev parent reply other threads:[~2011-10-11 15:38 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
2011-10-11 15:09 ` Henry Hirsch
2011-10-11 15:37 ` Nick Dokos [this message]
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).