From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Michael Behr <mkbehr@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Can't export subtree with links to headlines outside of the subtree [8.3.1 (8.3.1-95-g1dbb25-elpa)]
Date: Tue, 01 Sep 2015 20:29:53 +0200 [thread overview]
Message-ID: <871tei2dsu.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAGAuHdOh4d4PUp5gh1XC9iqq6qeH4OS-des8kr9-406cRYGyxQ@mail.gmail.com> (Michael Behr's message of "Tue, 1 Sep 2015 14:14:49 -0400")
Hello,
Michael Behr <mkbehr@gmail.com> writes:
> I want to export a subtree of a file, but that subtree has links to
> headings in the file that are outside of the subtree. I expect the
> exporting process to produce some sort of valid result, but instead it
> throws an "Unable to resolve link" error. Here's a test file to
> reproduce:
>
> * Foo
> * Bar :export:
> [[*Foo][Foo]]
>
> Making a file with those contents and trying to export it to e.g.
> latex will fail, but if the :export: tag is removed, exporting
> succeeds. I can't easily get a backtrace because the error comes from
> user-error, but it happens in org-export-resolve-fuzzy-link.
>
> Of course the exported file can't link to a target that doesn't exist,
> but it's probably better to strip out the link in this case than to
> throw an error, right?
Actually, wrong. It was discussed already, and the current trend is to
throw an error instead of silently dropping the link.
Can't you just filter it out before exporting?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2015-09-01 18:28 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-09-01 18:14 Bug: Can't export subtree with links to headlines outside of the subtree [8.3.1 (8.3.1-95-g1dbb25-elpa)] Michael Behr
2015-09-01 18:29 ` Nicolas Goaziou [this message]
2015-09-01 18:39 ` Michael Behr
2015-09-01 19:20 ` Nicolas Goaziou
2015-09-01 19:10 ` Marcin Borkowski
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=871tei2dsu.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=mkbehr@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).