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: Wed, 27 Sep 2023 10:35:26 +0200 [thread overview]
Message-ID: <m2ediknhdd.fsf@me.com> (raw)
In-Reply-To: <87zg198b8s.fsf@localhost>
Ihor Radchenko <yantar92@posteo.net> writes:
> You might as well use [[Link]].
For context, I use '#+OPTIONS: num:nil', which means that '[[link]]'
exports as 'link' and not a section number. I thought about using
'[[Link]]' as you suggest, but it would make almost all sentences I
write ungrammatical. For comparison, consider:
Properly capitalized:
The set of cellular membrane-bound organelles inside of the eukaryotic
cell that work together on the synthesis and distribution of proteins
and lipids.
Sentence-capitalized to make Org find the respective headings:
The set of Cellular membrane-bound Organelles inside of the Eukaryotic
cell that work together on the synthesis and distribution of Proteins
and Lipids.
> As for case sensitivity, it is something we might discuss. I just
> outlined the current state of the Org code.
Thank you for outlining the current state. I asked about it because I
have been struggling with this problem for a long time, and I was not
sure whether Org can or cannot do it, particularly given the fact that
my use of literal links is as simple as it gets.
If someone could fix this problem, say by adding link case-insensitivity
to '#+OPTIONS', I am willing to sponsor it financially, as the current
behavior is my biggest problem with the Org mode.
Rudy
--
"'Obvious' is all too often a synonym for 'wrong'."
-- Jeff Erickson, Algorithms, 2019
Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava
Slovakia
next prev parent reply other threads:[~2023-09-27 8:35 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č [this message]
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č
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=m2ediknhdd.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).