From: Juri Linkov <firstname.lastname@example.org>
To: Boruch Baum <email@example.com>
Subject: bug#42484: 26.1: org-mode should display value of links in mini-buffer
Date: Mon, 11 Jan 2021 20:54:57 +0200 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <20200723035629.7jg2pd2mhqjowvh4@E15-2016.optimum.net> (Boruch Baum's message of "Wed, 22 Jul 2020 23:56:29 -0400")
> In org-mode, when POINT is moved over an org-mode link, wouldn't it be
> reasonable for the value of that link to appear in the mini-buffer? The
> advantage of that is the user would know where the link points and what
> would happen if the link is opened (eg. would an external program open,
> would the network be queried).
I need this feature too to display not only links, but also
file names of generated images after executing SRC blocks.
So I've customized the option 'help-at-pt-display-when-idle'
to the value 't', and it displays the links and image file names
in the echo area.
Then later I noticed that it displays also useless help-echo
properties in other modes, e.g. on file names in Dired.
Fortunately, the same option allows to filter out such useless
properties by defining the property whose presence activates
displaying the help-echo property. I noticed that only
org-mode puts the property 'htmlize-link' on links.
So customizing 'help-at-pt-display-when-idle' to the value
'(htmlize-link) completely solves this problem.
next prev parent reply other threads:[~2021-01-11 19:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20200723035629.7jg2pd2mhqjowvh4@E15-2016.optimum.net>
2020-12-06 10:46 ` bug#42484: Updated patch Boruch Baum
2020-12-09 14:17 ` bug#42484: 26.1: org-mode should display value of links in minibuffer Boruch Baum
2021-01-11 18:54 ` Juri Linkov [this message]
2021-01-12 9:45 ` bug#42484: 26.1: org-mode should display value of links in mini-buffer Boruch Baum
2021-01-12 18:40 ` Juri Linkov
2021-01-13 5:40 ` Boruch Baum
2021-01-13 18:03 ` Juri Linkov
2021-01-13 21:18 ` Samuel Wales
2021-01-13 21:21 ` Samuel Wales
2021-01-13 21:22 ` Samuel Wales
2021-01-14 9:10 ` Juri Linkov
2021-01-14 21:02 ` Samuel Wales
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 \
* 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).