emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Rasmus <rasmus@gmx.us>
To: emacs-orgmode@gnu.org
Subject: Re: Bug: Export to html fails when link to header in non existing file in document present
Date: Wed, 06 May 2015 12:40:38 +0200	[thread overview]
Message-ID: <87oalyc7kp.fsf@gmx.us> (raw)
In-Reply-To: m2pp6e9mtw.fsf@krugs.de

Hi,

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

> more info and a reproducible example:
>
> when exporting the following org file
>
> * A link to a non existent file
>  [[file:~/NONEXISTENT.org::*SOMETHING][Link to header in non existing org file]]

What do you expect?

Should the "::*SOMETHING"-part be discarded without warning?

The internal link cannot be known without the file, as it is of the form
orgheadlineN where N=n+1 and n is the number of headlines prior to
"*Something"...

Though perhaps the #-construct should work, as we know the custom-id.

* A link to a non existent file
[[file:~/NONEXISTENT.org::#SOMETHING][Link to header in non existing org file]]

—Rasmus

-- 
Vote for proprietary math!

  reply	other threads:[~2015-05-06 10:40 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   ` Rasmus [this message]
2015-05-06 12:14     ` Bug: Export to html fails when link to header in non existing file in document present 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

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=87oalyc7kp.fsf@gmx.us \
    --to=rasmus@gmx.us \
    --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).