emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: "Ihor Radchenko" <yantar92@posteo.net>,
	"Rudolf Adamkovič" <salutis@me.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Case insensitivity of simple [[links]]
Date: Tue, 20 Aug 2024 22:10:20 +0200	[thread overview]
Message-ID: <87jzgbnefn.fsf@no.lan> (raw)
In-Reply-To: <87sf6dbmrp.fsf@localhost>

Hi Ihor, Rudolf,
* Ihor Radchenko <yantar92@posteo.net> [2023-10-14; 09:01 GMT]:
> Rudolf Adamkovič <salutis@me.com> writes:
>
>>> 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.
>
> 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.

actually this workaround does /not/ work
around if [link] does not point to a
heading but to a direct target <<link>>,
which is my usage scenario.

I asked in [1] for exporting [[link]] to
be exported (at least in HTML, PDF, ODT,
IMHO in any case) to a link rendered as
"link" not as a number.  In case of a
numbered heading/object it should render
as the heading/object, e.g. "5. link" if
the heading/object is the fifth.

My reasoning is similar to Rudolfs plea
for case-insensitive links: typing
[[link]] is so much easier and better to
read, than my workaround [[link][link]],
which renders as "link" (at least in
HTML export).



    As a side note: ASCII export might be
    tricky, though.  ATM this:
    
        #+LANGUAGE:    en
        
        These are three links: [[cat]], [[flower]], [[heast][heast]].
        
        
        - <<cat>> Cat :: An animal.
        - <<flower>> Flower :: a plant.
        - <<heast>> Heast :: We don't know, used for baking and brewing.
    
    
    exports as UTF text to:
    
    
        These are three links: 1, 2, [heast].
        
        
        Cat
              An animal.
        Flower
              a plant.
        Heast
              We don't know, used for baking and brewing.
        
        
        [heast] Unknown reference

    Which is not that helpful.

    Thinking about it, it might be
    helpful, if there was an option to
    export "<<target>>" as "target" (in
    all export backends).

Regards, Gregor



[1] https://list.orgmode.org/orgmode/87plq3nslb.fsf@no.lan/


  parent reply	other threads:[~2024-08-20 20:12 UTC|newest]

Thread overview: 18+ 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č
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
2024-06-20 13:51                       ` Rudolf Adamkovič
2024-08-20 20:10               ` Gregor Zattler [this message]
2024-10-19 13:46                 ` 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=87jzgbnefn.fsf@no.lan \
    --to=telegraph@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=salutis@me.com \
    --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).