emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Rainer M Krug <Rainer@krugs.de>
Cc: emacs-orgmode@gnu.org, Rasmus <rasmus@gmx.us>
Subject: Re: Bug: Export to html fails when link to header in non existing file in document present
Date: Thu, 07 May 2015 22:18:08 +0200	[thread overview]
Message-ID: <87wq0kgn0f.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <m2r3qsk8zh.fsf@krugs.de> (Rainer M. Krug's message of "Thu, 07 May 2015 11:55:14 +0200")

Rainer M Krug <Rainer@krugs.de> writes:

> Nicolas Goaziou <mail@nicolasgoaziou.fr> writes:
>
>> Hello,
>>
>> Rasmus <rasmus@gmx.us> writes:
>>
>>> Actually, the error you found is more interesting than what I first
>>> though, as any link with anchors will trigger the error, it seems.
>>> org-publish-cache must be non-nil, which seems to linger on publishing a
>>> project.
>>
>> Correct. External references can only be solved using publishing.
>>
>>> From 8e1dd6c43e8a358a85a8034825c475199bd2ffb7 Mon Sep 17 00:00:00 2001
>>> From: Rasmus <rasmus@gmx.us>
>>> Date: Wed, 6 May 2015 15:44:26 +0200
>>> Subject: [PATCH] ox-html: Improve links with search
>>>
>>> * ox-html.el (org-html-link): Handle links with search when
>>>   not using Publish.
>>
>> Thank you.
>>
>> However, I "fixed" it at ox-publish.el's level in
>> e42c1611094a689f77f09cc66c5a50fb1e3ac7bb instead, and throw an error
>> instead of a warning.
>
> OK - I can see the error now:
>
> ,----
> | user-error: Reference "29" in file "inst/matlab/org/profil5.m" cannot be resolved without publishing
> `----
>
> This helps finding it - thanks.
> I don't think it would be possible to give a line number for the org
> file where the link is?

This is not possible.

> Or is it possible to jump directly in org to reference "29"?

You may use `org-open-link-from-string'.

> What would be really nice is an option which makes it possible to export
> the file to html and just leave the non-resolvable links as
> non-resolvable links in the html and gives a list of all warnings for
> this links.

I changed the error into a message, with a dummy link.


Regards,

      reply	other threads:[~2015-05-07 20:16 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-05-04 11:47 Bug: Error export to html - "Org-publish-cache-get: `org-publish-cache-get' called, but no cache present" [8.3beta (release_8.3beta-1115-g8f3946 @ /Users/rainerkrug/.emacs.d/org-mode/lisp/)] Rainer M Krug
2015-05-06  7:39 ` Bug: Export to html fails when link to header in non existing file in document present WAS: " Rainer M Krug
2015-05-06 10:40   ` Bug: Export to html fails when link to header in non existing file in document present Rasmus
2015-05-06 12:14     ` Rainer M Krug
2015-05-06 13:50       ` Rasmus
2015-05-06 23:04         ` Nicolas Goaziou
2015-05-07  9:55           ` Rainer M Krug
2015-05-07 20:18             ` 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

  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=87wq0kgn0f.fsf@nicolasgoaziou.fr \
    --to=mail@nicolasgoaziou.fr \
    --cc=Rainer@krugs.de \
    --cc=emacs-orgmode@gnu.org \
    --cc=rasmus@gmx.us \
    /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).