emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Thibault Marin <thibault.marin@gmx.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Problem exporting file with code references
Date: Sat, 27 Aug 2016 00:47:17 -0500	[thread overview]
Message-ID: <87mvjyoja2.fsf@dell-desktop.WORKGROUP> (raw)

Hi list,

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)
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.

I get this failure with version:
Org-mode version 8.3.5 (release_8.3.5-1079-g61dd51.dirty @

For reference, the same file get exported without issue when using an
older version:
Org-mode version 8.3.5 (8.3.5-elpaplus @

Am I missing something here? Is this a bug?

Any help would be greatly appreciated.


             reply	other threads:[~2016-08-27  5:47 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-08-27  5:47 Thibault Marin [this message]
2016-08-28  9:57 ` Problem exporting file with code references Nicolas Goaziou

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:

  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=87mvjyoja2.fsf@dell-desktop.WORKGROUP \
    --to=thibault.marin@gmx.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).