From: Yuri Khan <yuri.v.khan@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: Boruch Baum <boruch_baum@gmx.com>,
Emacs developers <emacs-devel@gnu.org>
Subject: Re: display value of links in mini-buffer (was: Re: bug archiving policy)
Date: Sun, 6 Dec 2020 19:04:22 +0700 [thread overview]
Message-ID: <CAP_d_8WezomrMT6U+H5_R8P9d3=_Vm98S_4y0Hw-oTaL5n+hsA@mail.gmail.com> (raw)
In-Reply-To: <83zh2r9n26.fsf@gnu.org>
On Sun, 6 Dec 2020 at 18:44, Eli Zaretskii <eliz@gnu.org> wrote:
> > However, some modes also put 'help-echo property over text in a
> > buffer: buttons and links in Customize, links in Info, links in Eww,
> > diagnostics in Flymake. All of them would benefit from the behavior
> > you’re asking of Org: display tooltip text in the echo area when point
> > enters text so propertized.
>
> That could be annoying in some modes that have a lot of these
> help-echo properties. For example, in Dired you will see a lot of
> traffic in the echo-area if the help-echo text at point will be
> displayed there, because point generally moves there between file
> names, each of which has a help-echo on it.
Yes, because the Dired 'help-echo text is pretty useless:
mouse-1: visit this file in other window
I pretty much live in Dired with ‘dired-hide-details’ turned on most
of the time; it would be great to have the details (size and mode or
symlink target) in the echo area.
next prev parent reply other threads:[~2020-12-06 12:04 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-06 10:54 display value of links in mini-buffer (was: Re: bug archiving policy) Yuri Khan
2020-12-06 11:07 ` Boruch Baum
2020-12-06 11:26 ` Eli Zaretskii
2020-12-06 11:35 ` Boruch Baum
2020-12-06 11:39 ` Eli Zaretskii
2020-12-06 11:51 ` Yuri Khan
2020-12-06 12:03 ` Eli Zaretskii
2020-12-06 11:44 ` Eli Zaretskii
2020-12-06 12:04 ` Yuri Khan [this message]
2020-12-06 12:20 ` Eli Zaretskii
[not found] <<CAP_d_8XG7BrPqC3ZsqijLZerTOgPwt_MeBZOkDCbCuk6_cgGKQ@mail.gmail.com>
[not found] ` <<83zh2r9n26.fsf@gnu.org>
[not found] ` <<CAP_d_8WezomrMT6U+H5_R8P9d3=_Vm98S_4y0Hw-oTaL5n+hsA@mail.gmail.com>
[not found] ` <<83wnxv9lcy.fsf@gnu.org>
2020-12-06 16:42 ` Drew Adams
2020-12-06 18:27 ` Boruch Baum
2020-12-06 19:58 ` Drew Adams
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.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAP_d_8WezomrMT6U+H5_R8P9d3=_Vm98S_4y0Hw-oTaL5n+hsA@mail.gmail.com' \
--to=yuri.v.khan@gmail.com \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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
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.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).