emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Berry, Charles" via "General discussions about Org-mode." <emacs-orgmode@gnu.org>
To: Okam <okamsn+emacs-org@protonmail.com>
Cc: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Org failing to format a link with verbatim text
Date: Tue, 16 Feb 2021 23:52:33 +0000	[thread overview]
Message-ID: <03D50C6E-50A5-4D4A-BB71-B8C1DBAFAC0E@health.ucsd.edu> (raw)
In-Reply-To: <009a7aa5-3b23-b79a-9e65-a3a1bce645d7@protonmail.com>

> On Feb 16, 2021, at 1:20 PM, Okam <okamsn+emacs-org@protonmail.com> wrote:
> I am using the Emacs gccemacs branch with Org version "9.5-dev".
> I have noticed that when I try to insert the stored link
>     file:doc/loopy-doc.org::*Destructuring with =dash=
> and use the heading as the link description, that Org cannot format this 
> link correctly in all circumstances, and tries to make the verbatim text 
> break out from the link.

The last para of (info "(org) External Links") says in part:

If spaces must be part of the link (for example in
‘bbdb:R.*Stallman’), or if you need to remove ambiguities about the
end of the link, enclose the link in square or angular brackets.

To me, this sounds like advice not to drop external links amid normal text. i.e. put them in brackets instead.



  reply	other threads:[~2021-02-16 23:53 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-16 21:20 Org failing to format a link with verbatim text Okam
2021-02-16 23:52 ` Berry, Charles via General discussions about Org-mode. [this message]
     [not found]   ` <4d4823eb-926a-0b5b-a594-69b8d3c9cbe8@protonmail.com>
     [not found]     ` <200F8C74-6673-4EF4-A8DC-A45C5E865A2A@health.ucsd.edu>
2021-02-18  0:25       ` Okam
2021-02-18  2:19         ` Samuel Wales
2021-02-18  3:15         ` Berry, Charles via General discussions about Org-mode.

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=03D50C6E-50A5-4D4A-BB71-B8C1DBAFAC0E@health.ucsd.edu \
    --to=emacs-orgmode@gnu.org \
    --cc=ccberry@health.ucsd.edu \
    --cc=okamsn+emacs-org@protonmail.com \


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