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: No-description <<target>> links
Date: Sun, 22 Oct 2023 23:01:46 +0200	[thread overview]
Message-ID: <m27cnee5hh.fsf@me.com> (raw)
In-Reply-To: <87lebvawnn.fsf@localhost>

Ihor Radchenko <yantar92@posteo.net> writes:

> I think that we may need to introduce a customization for default link
> description. Some backends hard-code the default description to
> something non-trivial and some just use arbitrary fallback like ???
> (ox-ascii), "No description" (ox-html), or "" (ox-latex).

I wonder, why not export [[link]] to <<link>> as "link" by default, if
no description is given, as is the case with URLs, Elisp, and the like?
And if that is not desirable, would the new customization allow for
doing that?

I am asking the second question because I am still hoping to solve my
problem with the impracticality of [[Literal link][literal link]]s in
densely linked text, as explained in my other thread.  If Org could
export [[link]] to <<link>> as "link", and offered a STARTUP for literal
links, then that would fix my problem for good.

Thank you!

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

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

next prev parent reply	other threads:[~2023-10-22 21:02 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-21 11:22 No-description <<target>> links Rudolf Adamkovič
2023-10-22  8:28 ` Ihor Radchenko
2023-10-22 21:01   ` Rudolf Adamkovič [this message]
2023-10-23  8:15     ` Ihor Radchenko
2023-10-24  8:15       ` Max Nikulin
2023-10-24  9:34         ` 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=m27cnee5hh.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

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).