From: "Steven Bagley" <firstname.lastname@example.org>
To: "Nicolas Goaziou" <email@example.com>, Bastien <firstname.lastname@example.org>
Subject: Re: Bug: Double colon in org link description breaks the link [9.4.4 (release_9.4.4 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)]
Date: Mon, 03 May 2021 09:29:28 -0700 [thread overview]
Message-ID: <email@example.com> (raw)
I am aware of the meaning of "::". Is this a design decision or an implementation constraint? My intuition, obviously wrong here, is that link, being a special kind of object, should have priority over what amounts to a formatting command.
On Mon, May 3, 2021, at 08:59, Nicolas Goaziou wrote:
> Bastien <firstname.lastname@example.org> writes:
> > Hi Steven,
> > "Steven Bagley" <email@example.com> writes:
> >> In emacs -Q:
> >> 1. M-x org-mode
> >> 2. insert the following line in the buffer (created by
> >> org-mac-grab-link)
> >> - [[https://rgoswami.me/posts/org-note-workflow/][An Orgmode Note
> >> Workflow :: Rohit Goswami Reflections]]
> >> 3. You can't follow the link using mouse-left because of the "::" in
> >> the link, which makes that line into an org "description list
> >> item". The message is "No link found".
> > Confirmed, thanks for the reproducible recipe.
> An item bullet followed by two colons is a special syntax in Org. It has
> precedence over the link.
> Besides saying "don't do that", the usual trick is to insert a zero
> width space between the two colons.
> Nicolas Goaziou
next prev parent reply other threads:[~2021-05-03 16:30 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-02 22:00 Steven Bagley
2021-05-03 4:03 ` Bastien
2021-05-03 15:59 ` Nicolas Goaziou
2021-05-03 16:29 ` Steven Bagley [this message]
2021-05-03 17:30 ` Nicolas Goaziou
2021-05-03 18:39 ` Steven Bagley
2021-05-03 19:33 ` Bastien
2021-05-04 20:27 ` Bastien
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).