emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
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: Fri, 06 Oct 2023 12:43:56 +0200	[thread overview]
Message-ID: <m2pm1skp3n.fsf@me.com> (raw)
In-Reply-To: <87edi9i3by.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

>> For context, I use '#+OPTIONS: num:nil', which means that '[[link]]'
>> exports as 'link' and not a section number.
>
> I am confused. num:nil just means that section titles will not be
> numbered. It has nothing to do with links, AFAIK.

My sentence says it all, but if that is not clear, consider:

EXAMPLE 1:

  This is a [[test]] link.
  
  * test

EXPORT OF EXAMPLE 1:

  This is a 1 link.

EXAMPLE 2:

  #+OPTIONS: num:nil
  
  This is a [[test]] link.
  
  * test

EXPORT OF EXAMPLE 2:

  This is a test link.

> What about [[Link][link]]?

That makes Org documents hard to read in *plain text*, that is without
the "descriptive links" fontification.  Here is my note again, compare:

EXAMPLE 1: Hard-to-read, unhelpful markup:

  The set of [[Cellular membrane][cellular membrane]]-bound
  [[Organelle][organelle]]s inside of the [[Eukaryotic cell][eukaryotic
  cell]] that work together on the synthesis and distribution of
  [[Protein][protein]]s and [[Lipid][lipid]]s.

EXAMPLE 2: Lightweight, helpful markup:

  The set of [[cellular membrane]]-bound [[organelle]]s inside of the
  [[eukaryotic cell]] that work together on the synthesis and
  distribution of [[protein]]s and [[lipid]]s.

> Judging from your example, I am not sure if it is an actual problem
> with Org mode. I am still to see a use case when case-insensitivity
> would be useful. Now, I am inclined to fix the docstring (and possibly
> the manual), clarifying about case-sensitivity of the internal links.

For me, this is not only "an actual problem with Org" but the biggest
problem, and the only big problem, I have with Org.

As a markup language, Org is "99% there" in having some of the *most
practical* plain text [[link]]s available, but then falls short on case
sensitivity, ending up with the exact opposite.

Now, I could use descriptive links, which hide the [[Wart][wart]] behind
fontification tricks, but that would not solve my problem.  Why?  I need
to use other plain text tools, such as Git, with my densely linked Org
documents.

Rudy
-- 
"Simplicity is complexity resolved."
-- Constantin Brâncuși, 1876-1957

Rudolf Adamkovič <salutis@me.com> [he/him]
Studenohorská 25
84103 Bratislava
Slovakia


  reply	other threads:[~2023-10-06 10:45 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č [this message]
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=m2pm1skp3n.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).