emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bernt Hansen <bernt@norang.ca>
To: David Maus <dmaus@ictsoc.de>
Cc: emacs-orgmode@gnu.org
Subject: Re: Re: BUG-Export level 1 subtree fails
Date: Mon, 01 Nov 2010 15:19:24 -0400	[thread overview]
Message-ID: <87mxpsq2bn.fsf@gollum.intra.norang.ca> (raw)
In-Reply-To: <87eib4n9qm.wl%dmaus@ictsoc.de> (David Maus's message of "Mon, 01 Nov 2010 20:07:29 +0100")

David Maus <dmaus@ictsoc.de> writes:

> At Sun, 31 Oct 2010 20:34:20 -0400,
> Bernt Hansen wrote:
>>
>> Bernt Hansen <bernt@norang.ca> writes:
>>
>> > Hi,
>> >
>> > Using the following commit
>> > ed5665e (babel: Use `copy-sequence' instead of `copy-tree', 2010-10-31)
>> >
>> > if I mark a level 1 subtree with C-c @ and then try to export to HTML
>> > with C-c C-e b I get the following stack dump:
>> >
>> > Exporting a level 2 subtree works.
>>
>> This seems to be related to my use of archive properties.
>
> Not exactly.  If you export a subtree, Org uses the heading as the
> exported document's title and marks the headline for removal by
> the :org-license-to-kill text property.
>
> Now the error kicks in `org-export-remove-archived-trees' because at
> this point the headline is already removed but the function is set to
> 'headline, e.g. tries to export this headline.
>
> Not sure how to solve this problem.

I believe Carsten has a fix for this:

adede9f (Fix export bug of a region with an ARCHIVE property set, 2010-11-01)

but I haven't verified it yet.

Regards,
Bernt

  reply	other threads:[~2010-11-01 19:19 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-01  0:24 BUG-Export level 1 subtree fails Bernt Hansen
2010-11-01  0:34 ` Bernt Hansen
2010-11-01 19:07   ` David Maus
2010-11-01 19:19     ` Bernt Hansen [this message]
2010-11-01 20:28       ` David Maus
2010-11-01 20:47         ` Bernt Hansen

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=87mxpsq2bn.fsf@gollum.intra.norang.ca \
    --to=bernt@norang.ca \
    --cc=dmaus@ictsoc.de \
    --cc=emacs-orgmode@gnu.org \
    /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).