From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode@gnu.org
Subject: [FR] stable literal hrefs in HTML export of direct links and usage of link description instead of numbered links in case of shortend link syntax
Date: Tue, 20 Aug 2024 17:04:32 +0200 [thread overview]
Message-ID: <87plq3nslb.fsf@no.lan> (raw)
Dear org-mode developers, this is
a twofold feature request:
I write a piece documentation with a
glossary in form of a description list
and want to able to link to the
descriptions. The thing is then
exported to HTML.
The only way to do that I found was with
direct links, but this
1. does not allow for stable hrefs
2. and numbers the link text if the
abbreviated org link syntax [[link]]
is used:
This
An Emacs [[frame]] may be
opened...
- <<frame>> frame :: This is ancient
terminology...
This renders into (among other things):
<div id="content" class="content">
<p>
An Emacs <a href="#orgc6125eb">1</a> may be
opened…
</p>
<dl class="org-dl">
<dt><a id="orgc6125eb"></a> frame</dt><dd>This is ancient
terminology…</dd>
</dl>
</div>
Since in the org-mode document the
author has to care for the
unambiguousness of the link anyway I
would expect:
1. that instead of a random id the link
description is used as a href and
therefore be stable between different
exports, and
2. the link description is used instead
of a number in case of a shortened
[[link]].
The second effect does not show up, if
[[link][link]] is used instead of
[[link]] but this is tedious to type
and IMHO unneccesary.
If this feature request are not / cannot
be met: Is there a workaround to at
least achive the goal of stable href
links?
Thanks for org-mode and your attention, Gregor
next reply other threads:[~2024-08-20 15:06 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-20 15:04 Gregor Zattler [this message]
2024-08-20 18:47 ` [FR] stable literal hrefs in HTML export of direct links and usage of link description instead of numbered links in case of shortend link syntax Ihor Radchenko
2024-08-21 16:51 ` Ihor Radchenko
2024-09-02 11:00 ` Gregor Zattler
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=87plq3nslb.fsf@no.lan \
--to=telegraph@gmx.net \
--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).