From: Carsten Dominik <carsten.dominik@gmail.com>
To: Bernt Hansen <bernt@norang.ca>
Cc: Carsten Dominik <carsten@orgmode.org>, emacs-orgmode@gnu.org
Subject: Re: Problem with CUSTOM_ID persistence during exporting
Date: Sun, 19 Apr 2009 22:32:48 +0200 [thread overview]
Message-ID: <56EEDA07-E0A6-4DAD-9AD4-1FDEB364ECF8@gmail.com> (raw)
In-Reply-To: <87skk4r3c5.fsf@gollum.intra.norang.ca>
Yes, this was a bug, fixed now.
Thanks
- Carsten
On Apr 19, 2009, at 6:54 PM, Bernt Hansen wrote:
> Hi Carsten,
>
> I noticed a problem with custom ids that should probably be fixed.
>
> I was playing with a temporary custom id for a document - so I added
> it
> and exported. Then when I removed the id it's still there. The
> org-export-preferred-target-alist still has the mapping of section
> number to preferred id which I removed. I think it also applies to
> different documents.
>
> I think the variables
>
> (defvar org-export-target-aliases nil
> "Alist of targets with invisible aliases.")
> (defvar org-export-preferred-target-alist nil
> "Alist of section id's with preferred aliases.")
> (defvar org-export-code-refs nil
> "Alist of code references and line numbers")
>
> should probably all be set to nil before export processing of any
> file.
> These collect values during the export process which affects future
> exports.
>
> I think it's possible to set a CUSTOM_ID is section 1 on document X
> and
> have it apply to document Y if you export document Y after document X.
>
> This just feels wrong to me.
>
> All export functions should probably call some org-exp-init function
> to
> clear these (and maybe other vars) using during the export process.
>
> What do you think?
>
> -Bernt
prev parent reply other threads:[~2009-04-19 20:33 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-04-19 16:54 Problem with CUSTOM_ID persistence during exporting Bernt Hansen
2009-04-19 20:32 ` Carsten Dominik [this message]
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=56EEDA07-E0A6-4DAD-9AD4-1FDEB364ECF8@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=bernt@norang.ca \
--cc=carsten@orgmode.org \
--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).