From: "Rudolf Adamkovič" <salutis@me.com>
To: Ihor Radchenko <yantar92@posteo.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: Case insensitivity of simple [[links]]
Date: Thu, 19 Oct 2023 12:30:49 +0200 [thread overview]
Message-ID: <m2mswe6h0m.fsf@me.com> (raw)
In-Reply-To: <87jzrlfrql.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
>>> Note that there is generally no guarantee that [[name]] link will be
>>> exported as "name" by any particular backend. Your workaround with
>>> num:nil is just a workaround that may or may not work in future.
>>
>> I did not know this is considered a workaround! I have always thought
>> this is how Org is specified to work (as in tests).
Actually, dang! I spoke too soon. While links now work consistently
before and after exports, their description matches the destination
heading, not the source link. But if we case-fold now, it would make a
lot more sense to match the case of the source link, as it enables one
to link [[capitalized heading]]s. Otherwise, we case-fold with no
significant benefits, as far as I can see.
Without also fixing this part, my problem with Org remains. :(
>> [...] call to 'org-toggle-link-display' does nothing.
> It does nothing because it is one of the options that must be set before
> Org mode is loaded. Resolving buffer-local variables happens after the
> major mode is loaded.
I have noticed that 'org-use-extra-keys', for example, is documented as
"must set it before loading Org", but there is nothing similar in the
'org-link-descriptive' docstring. So perhaps this is a bug, not a
feature?
Upon a quick look, 'org-toggle-link-display' does exactly two things:
1. (setq org-link-descriptive (not org-link-descriptive)) and
2. (org-link-descriptive-ensure),
where 'org-link-descriptive-ensure' wraps exactly one expression:
(org-fold-core-set-folding-spec-property
(car org-link--link-folding-spec)
:visible (not org-link-descriptive))
Could Org execute this expression after loading a document, given the
buffer-local value of 'org-link-descriptive' necessitates it?
Rudy
--
"It is far better to have a question that can't be answered than an answer that
can't be questioned."
--- Carl Sagan
Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava
Slovakia
next prev parent reply other threads:[~2023-10-19 10:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-23 0:45 Case insensitivity of simple [[links]] Rudolf Adamkovič
2023-09-23 10:10 ` Ihor Radchenko
2023-09-24 14:46 ` Rudolf Adamkovič
2023-09-26 10:44 ` Ihor Radchenko
2023-09-27 8:35 ` Rudolf Adamkovič
2023-10-05 13:52 ` Ihor Radchenko
2023-10-06 10:43 ` Rudolf Adamkovič
2023-10-14 9:01 ` Ihor Radchenko
2023-10-16 20:28 ` Rudolf Adamkovič
2023-10-17 10:49 ` Ihor Radchenko
2023-10-19 10:30 ` Rudolf Adamkovič [this message]
2023-10-20 9:41 ` Ihor Radchenko
2023-10-21 11:40 ` Rudolf Adamkovič
2023-10-21 13:23 ` Ihor Radchenko
2023-12-09 12:17 ` 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
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=m2mswe6h0m.fsf@me.com \
--to=salutis@me.com \
--cc=emacs-orgmode@gnu.org \
--cc=yantar92@posteo.net \
/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).