emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Maxim Nikulin <manikulin@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: Internal link broken when publishing (was org-id with ox-html)
Date: Tue, 24 Aug 2021 22:23:24 +0700	[thread overview]
Message-ID: <sg32te$r48$1@ciao.gmane.io> (raw)
In-Reply-To: <1640082.E36kBsiRYQ@pluto>

On 23/08/2021 03:42, inkbottle wrote:
> Links between two different files, like
> `[[id:e54113f9-2ad7-4a86-94be-68ffc696de0b][hello]]`, get broken when
> publishing. (whatever the settings).
> I haven't found any workaround.
> Being able to move around entries, functionality provided by `org-id-link-to-
> org-use-id`, is pivotal, IMO.

 From my point of view it looks like a bug.
checks for ID property.
queries CUSTOM_ID only. I suppose, ID should be here as well. A subtle 
point is which one (ID or CUSTOM_ID) should be used if both are defined 
for some headers.

Maybe it is possible to create workaround as a custom config without 
touching of Org code. I guess, "nicer" ids may be replaced by values of 
ID property. Examples (I tried none of them):
https://orgmode.org/list/E1jxAjq-0004Dk-LH@lists.gnu.org/ (TEC. 
[Interest] Determanistic Org IDs. Sun, 19 Jul 2020 22:27:31 +0800)
(Tom Gillespie. Tue, 8 Dec 2020 20:39:08 -0500, Re: stability of toc links)
(Diego Zamboni. Wed, 9 Dec 2020 09:45:52 +0100. Re: stability of toc links)
(TRS-80. Sat, 12 Dec 2020 20:25:15 -0500. Re: Better heading links in 
org-mode exports)
- https://writequit.org/articles/emacs-org-mode-generate-ids.html

  reply	other threads:[~2021-08-24 15:24 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-08-13 22:28 org-id with ox-html inkbottle
2021-08-14  0:50 ` inkbottle
2021-08-14  4:20   ` inkbottle
2021-08-17  3:11     ` Internal link broken when publishing (was org-id with ox-html) inkbottle
2021-08-22 20:42       ` inkbottle
2021-08-24 15:23         ` Maxim Nikulin [this message]
2021-09-07 15:46           ` chris
2021-09-14 16:33             ` Max Nikulin
2021-09-20  0:05               ` chris
2021-09-20 14:13                 ` Max Nikulin
2021-09-20 15:26                   ` chris

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='sg32te$r48$1@ciao.gmane.io' \
    --to=manikulin@gmail.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).