all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: "Rudolf Adamkovič" <rudolf@adamkovic.org>
Cc: emacs-orgmode@gnu.org
Subject: Re: Org exports broken ID links
Date: Sat, 31 Aug 2024 15:14:54 +0000	[thread overview]
Message-ID: <87plpolo5t.fsf@localhost> (raw)
In-Reply-To: <m2wmjycoj5.fsf@adamkovic.org>

Rudolf Adamkovič <rudolf@adamkovic.org> writes:

> REPRODUCTION STEPS:
> ...
>      * Foo :noexport:
>      :PROPERTIES:
>      :ID: xxx
>      :END:
>      
>      * Bar
>      [[id:xxx][Foo]]
>   
>   3. Export the file as HTML using (`C-c C-e h o').
>
> EXPECTED:
>
>   The export stops due to a broken link, as per
>
>     `org-export-with-broken-links'.
>
> ACTUAL:
>
>   Org produces an HTML file with a link that points to nowhere.

That link is not broken - it points to a file containing the linked
heading. It just happens to be the same Org file.

The same mechanism is applied when you export a file with id: link that
points to _another_ Org file - the link will be created to that Org file.

Not a bug.
Canceled.

If you want a feature controlling whether to export fuzzy/id links to
Org files, feel free to open a feature request.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-08-31 15:14 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-08-30 10:07 Org exports broken ID links Rudolf Adamkovič
2024-08-31 15:14 ` Ihor Radchenko [this message]
2024-08-31 21:01   ` Rudolf Adamkovič
2024-09-01 13:15     ` Ihor Radchenko
2024-09-03 23:15       ` Rudolf Adamkovič
2024-09-08 17:57         ` Ihor Radchenko

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=87plpolo5t.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=rudolf@adamkovic.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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.