From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Thibault Marin <thibault.marin@gmx.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Problem exporting file with code references
Date: Sun, 28 Aug 2016 11:57:14 +0200 [thread overview]
Message-ID: <87a8fxxll1.fsf@saiph.selenimh> (raw)
In-Reply-To: <87mvjyoja2.fsf@dell-desktop.WORKGROUP> (Thibault Marin's message of "Sat, 27 Aug 2016 00:47:17 -0500")
Hello,
Thibault Marin <thibault.marin@gmx.com> writes:
> I am trying to run the last example on the documentation page:
> http://orgmode.org/manual/Literal-examples.html and I am running into a
> problem. The following is the full org file I am trying to export:
>
> ---
> #+BEGIN_SRC emacs-lisp -n -r
> (save-excursion (ref:sc)
> (goto-char (point-min))) (ref:jump)
> #+END_SRC
> In line [[(sc)]] we remember the current position. [[(jump)][Line
> (jump)]] jumps to point-min.
> ---
>
> When trying to export (I tried html or latex), I get the following error
> message: 'user-error: Unable to resolve link: "sc"'.
>
> Trying to investigate, it appears that the `org-babel--normalize-body'
> function (ob-core.el) removes the references "(ref:sc)" and "(ref:jump)"
> from the code block prior to execution. This happens during the call to
> `org-babel-exp-process-buffer' when `org-export-babel-evaluate' is
> non-nil (in ox.el). From that point, the source block content does not
> contain the "(ref:sc)" and "(ref:jump)" text. Consequently, when
> reaching the `org-export-resolve-coderef' function, the link is not
> found in the code and the error is returned.
This is now fixed. Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2016-08-28 9:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-27 5:47 Problem exporting file with code references Thibault Marin
2016-08-28 9:57 ` Nicolas Goaziou [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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87a8fxxll1.fsf@saiph.selenimh \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=thibault.marin@gmx.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.