emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Gregor Zattler <telegraph@gmx.net>
To: 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 14:09:43 +0100	[thread overview]
Message-ID: <87sf2qhlyg.fsf@no.lan> (raw)
In-Reply-To: <871qaahocg.fsf@localhost>

Hi Ihor, Omar, 
* Ihor Radchenko <yantar92@posteo.net> [2024-01-21; 12:18 GMT]:
> Omar Antolín Camarena <omar@matem.unam.mx> writes:
>
>> If you have an org link with a newline embedded in the description in an org-mode buffer and put point on it, org-open-at-point correctly follows the link but org-open-at-point-global does not, it instead reports "No link found". (I have plenty of org links with newlines in the description, because org-fill-paragraph tends to reformat links that way.)
>
> Thanks for reporting!
> Fixed, on main.
> https://git.savannah.gnu.org/cgit/emacs/org-mode.git/commit/?id=ac1c72376

that works for me now with both, org-open-at-point in
org-mode buffers and org-open-at-point-global somewhere
else.

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!?

Regards, Ggregor

next prev parent reply	other threads:[~2024-01-21 13:11 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 [this message]
2024-01-21 13:27     ` Ihor Radchenko
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=87sf2qhlyg.fsf@no.lan \
    --to=telegraph@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    /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

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