emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Ihor Radchenko <yantar92@posteo.net>
To: Gregor Zattler <telegraph@gmx.net>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] org-open-at-point-global fails on links with multiline descriptions in org-mode buffers [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)]
Date: Sun, 21 Jan 2024 13:27:44 +0000	[thread overview]
Message-ID: <87plxug6jz.fsf@localhost> (raw)
In-Reply-To: <87sf2qhlyg.fsf@no.lan>

Gregor Zattler <telegraph@gmx.net> writes:

> But how about this idea of Omar: 
>
> "I would like to suggest that org-open-at-point-global
> check to see if it is being run in an Org mode buffer
> and if so just call org-open-at-point.  That way users
> can bind org-open-at-point-global and use that key
> binding everywhere including org-mode buffers without
> loss of functionality compared to org-open-at-point."
>
> This sounds reasonable for me!?

That would be a breaking change.
`org-open-at-point-global' is more permissive compared to
`org-open-at-point'. For example, `org-open-at-point-global' would open
links inside verbatim or src blocks, while `org-open-at-point' would not.

-- 
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>


  reply	other threads:[~2024-01-21 13:25 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-01-20 19:44 [BUG] org-open-at-point-global fails on links with multiline descriptions in org-mode buffers [9.6.6 (release_9.6.6 @ /usr/share/emacs/29.1/lisp/org/)] Omar Antolín Camarena
2024-01-21 12:18 ` Ihor Radchenko
2024-01-21 13:09   ` Gregor Zattler
2024-01-21 13:27     ` Ihor Radchenko [this message]
2024-01-21 17:50   ` Omar Antolín Camarena

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=87plxug6jz.fsf@localhost \
    --to=yantar92@posteo.net \
    --cc=emacs-orgmode@gnu.org \
    --cc=telegraph@gmx.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
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

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