emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Steven Bagley" <stevenbagley@fastmail.fm>
To: "Nicolas Goaziou" <mail@nicolasgoaziou.fr>
Cc: Bastien <bzg@gnu.org>, emacs-orgmode@gnu.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 11:39:38 -0700	[thread overview]
Message-ID: <d24d276e-b52c-4b57-b4ec-8f2144f92cb8@www.fastmail.com> (raw)
In-Reply-To: <878s4v7miw.fsf@nicolasgoaziou.fr>

Yes, that works for the example I quoted. The source of the original "::" is org-mac-link, not my typing. Maybe that could insert a different character sequence to avoid any confusion.


On Mon, May 3, 2021, at 10:30, Nicolas Goaziou wrote:
> "Steven Bagley" <stevenbagley@fastmail.fm> writes:
> > 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.
> - ... :: is also a special kind of syntax. It starts before the link
>   (and being a block element, it even has priority over link).
> Have you tried the solution I gave you?
> Regards,

  reply	other threads:[~2021-05-03 18:51 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-05-02 22:00 Bug: Double colon in org link description breaks the link [9.4.4 (release_9.4.4 @ /Applications/Emacs.app/Contents/Resources/lisp/org/)] Steven Bagley
2021-05-03  4:03 ` Bastien
2021-05-03 15:59   ` Nicolas Goaziou
2021-05-03 16:29     ` Steven Bagley
2021-05-03 17:30       ` Nicolas Goaziou
2021-05-03 18:39         ` Steven Bagley [this message]
2021-05-03 19:33           ` Bastien
2021-05-04 20:27           ` Bastien

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:

  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=d24d276e-b52c-4b57-b4ec-8f2144f92cb8@www.fastmail.com \
    --to=stevenbagley@fastmail.fm \
    --cc=bzg@gnu.org \
    --cc=emacs-orgmode@gnu.org \
    --cc=mail@nicolasgoaziou.fr \


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