From: Philipp Kroos <philipp.kroos@t-online.de>
To: Suvayu Ali <fatkasuvayu+linux@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: subtree-export limitations
Date: Sat, 17 Nov 2012 13:25:20 +0100 [thread overview]
Message-ID: <87lie0bemn.fsf@t-online.de> (raw)
In-Reply-To: <20121116163645.GF24384@kuru.dyndns-at-home.com> (Suvayu Ali's message of "Fri, 16 Nov 2012 17:36:45 +0100")
Ok, thanks to both of you. I'll stick with the workarounds pointed out
by Alan for now.
Anyway, I'm still curious if it wouldn't be feasible to treat
subtree-options more similar to inbuffer-options?
Maybe I'll have a look at that in some spare time, though I think my
understanding of the concepts might be insufficient yet. Any further
clues on this topic are much appreciated therfore!
Best regards, Philipp
Suvayu Ali <fatkasuvayu+linux@gmail.com> writes:
> On Fri, Nov 16, 2012 at 04:45:35PM +0100, Philipp Kroos wrote:
>>
>> So would be any other EXPORT_OPTIONS-line. The responsible function is
>> org-export--get-subtree-options, which builds a list of already seen
>> keywords. The lists members are then ignored if seen again.
>> Is there any particular reason why this is done?
>>
>
> Since Alan gave you a workaround, I will try to answer the why. I
> believe the reason behind this behaviour is properties are not designed
> to "accumulate" values. I believe there is a special case treatment for
> certain babel uses; as I'm hazy on the details, you have to look in the
> archives from about a year back (my memory tells me September 2011 to
> December 2011). You should look for discussions involving Rainer(?)
> and Eric Schulte.
>
> Hope this helps.
next prev parent reply other threads:[~2012-11-17 12:25 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-11-16 15:45 subtree-export limitations Philipp Kroos
2012-11-16 15:56 ` Alan Schmitt
2012-11-16 16:36 ` Suvayu Ali
2012-11-17 12:25 ` Philipp Kroos [this message]
2012-11-17 12:48 ` Nicolas Goaziou
2012-11-17 13:33 ` Nicolas Goaziou
2012-11-17 15:12 ` Philipp Kroos
2012-11-17 16:00 ` Nicolas Goaziou
2012-11-18 11:23 ` Philipp Kroos
2012-11-19 13:55 ` Alan Schmitt
2012-12-22 18:58 ` Bastien
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=87lie0bemn.fsf@t-online.de \
--to=philipp.kroos@t-online.de \
--cc=emacs-orgmode@gnu.org \
--cc=fatkasuvayu+linux@gmail.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).