emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Kyle Meyer <kyle@kyleam.com>
To: YH Tan <astyh83@gmail.com>
Cc: 44687@debbugs.gnu.org
Subject: bug#44687: 26.3; Link broken in inline comment
Date: Mon, 06 Dec 2021 22:15:47 -0500	[thread overview]
Message-ID: <8735n585r0.fsf@kyleam.com> (raw)
In-Reply-To: <85490A73-86DB-435E-AF7A-95361CF7EE14@gmail.com>

tags 44687 wontfix
close 44687

YH Tan writes:

> In org-mode,
> ```
> [[link]]@@comment:[[link]]@@
> # [[link]]
> * link
> ```
> I get the message "No Link Found" when clicking on the [[link]] within
> the inline @@comment:[[link]]@@.
> The link works fine with emacs -Q, but breaks after evaluating some
> init.el code.
> Problem is, I cannot pinpoint to the exact code that broke the link.

I'm sorry you didn't get a response at the time.

Your recipe starts complaining "No Link Found" as of Org's d3774fba7,
which was a part of the 9.2 release:

  Limit `org-open-at-point'
  * lisp/org.el (org-open-at-point): Do not open everything that looks
    like a link, in particular in verbatim or code objects.  However,
    still conveniently open links in comments, node properties and

The Org bundled with Emacs 26.3 was 9.1.9, so the difference you
reported between your regular environment and 'emacs -Q' is very likely
explained by the above commit being included in the Org available from
ELPA but not yet included in the Org that shipped with Emacs 26.3.

My understanding is that no longer being able to open a link (or rather
text that resembles a link) in an export snippet is an intentional
consequence of that commit, so I'm closing this as wontfix.  (But fwiw
calling org-open-at-point-global rather than org-open-at-point should
give the behavior you're after.)

           reply	other threads:[~2021-12-07  3:16 UTC|newest]

Thread overview: expand[flat|nested]  mbox.gz  Atom feed
 [parent not found: <85490A73-86DB-435E-AF7A-95361CF7EE14@gmail.com>]

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=8735n585r0.fsf@kyleam.com \
    --to=kyle@kyleam.com \
    --cc=44687@debbugs.gnu.org \
    --cc=astyh83@gmail.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).