emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Robert Klein <roklein@roklein.de>
To: emacs-orgmode@gnu.org
Subject: Unable to resolve info links during publishing
Date: Tue, 22 Dec 2015 12:35:29 +0100 (CET)	[thread overview]
Message-ID: <20151222.123529.2026390326868297759.roklein@roklein.de> (raw)

Hi,

when publishing a org document (to HTML), info links, e.g.
"info:org#Formula syntax for Lisp" throw errors, e.g.:

  Unable to resolve link "info:org#Formula syntax for Lisp"


The link exists and can be followed in the org document by pressing
the keys C-c C-o.

Org version is 8.3.2 maint.  I did a little bisection and ended up
with this commit:

dc08e98885015c27196843aeb62bde287da84873 is the first bad commit
commit dc08e98885015c27196843aeb62bde287da84873
Author: Jacob Gerlach <jacobgerlach@gmail.com>
Date:   Wed Mar 11 22:39:11 2015 -0400

    ox.el: Issue error for unresolved fuzzy link
    
    * lisp/ox.el (org-export-resolve-fuzzy-link): Throw an error instead
      of returning nil when link can't be resolved.
    
    * testing/lisp/test-ox.el (test-org-export/resolve-fuzzy-link): Change
      last test from should-not to should-error
    
    In addition to throwing an error, don't store the failed match in the
    link cache.
    
    TINYCHANGE

:040000 040000 3151cb8e3a5da171e93278c7fa5fd7aa82012e81 7ff2fffd50ed0587acf5ddb498493a7a16f6b549 M	lisp
:040000 040000 e362c6fb9e260a6d9b0212daac3c89cf12393642 b08d87de16cabd3416d8eefae2033e3081159218 M	testing


In fact I agree with the commit, but I don't understand why org can't
resolve the link...

Any help is very much appreciated.

Thanks and best regards
Robert

             reply	other threads:[~2015-12-22 11:35 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-12-22 11:35 Robert Klein [this message]
2015-12-22 12:49 ` Unable to resolve info links during publishing Nicolas Goaziou
2015-12-23 22:38   ` Robert Klein

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=20151222.123529.2026390326868297759.roklein@roklein.de \
    --to=roklein@roklein.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).