From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Yuri Khan <yuri.v.khan@gmail.com>
Cc: boruch_baum@gmx.com, emacs-devel@gnu.org
Subject: RE: display value of links in mini-buffer (was: Re: bug archiving policy)
Date: Sun, 6 Dec 2020 08:42:48 -0800 (PST) [thread overview]
Message-ID: <ab6f6667-4114-4352-ad83-4d677d42934b@default> (raw)
In-Reply-To: <<83wnxv9lcy.fsf@gnu.org>>
> > Yes, because the Dired 'help-echo text is pretty useless:
> > mouse-1: visit this file in other window
>
> You are entitled to your opinion, but others might disagree.
For one thing, it would be debatable just what file or dir
info to show in the echo area.
However, this is what Dired+ uses, in place of that echo text,
if `describe-file' is also available (library `help-fns+.el'):
mouse-1: visit in another window, C-h RET: describe
`C-h RET' then gives you info about the file/dir in *Help*:
z:/dir/for/foobar/stuff/
------------------------
File Type: Normal file
Permissions: -rw-rw-rw-
Size in bytes: 809215
Time of last access: Sat Dec 5 10:02:55 2020 (Pacific Standard Time)
Time of last modification: Sat Dec 5 10:02:55 2020 (Pacific Standard Time)
Time of last status change: Sat Dec 5 09:27:17 2020 (Pacific Standard Time)
Number of links: 1
User ID (UID): 37786
Group ID (GID): 513
Inode: 2814749767263948
Device number: 315267003
And if the file is the name of an autofile bookmark (library
`Bookmark+'), then it also shows the bookmark information
(tags etc.):
Bookmark `foobar.el'
--------------------
File: foobar.el
Directory: z:/dir/for/foobar/stuff/
Position: 0
Tags:
"blue"
"white"
There's only so much info that can be usefully put in
a help echo. Info about possible actions (keys, mouse
events) _is_ helpful, IMO, even if in some cases that
info might be standard/trivial. If some of those keys
or mouse actions provide help, however, that's a good
to make help available, and it's not limited to the
echo-area space.
next parent reply other threads:[~2020-12-06 16:42 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[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 [this message]
2020-12-06 18:27 ` display value of links in mini-buffer (was: Re: bug archiving policy) Boruch Baum
2020-12-06 19:58 ` Drew Adams
2020-12-06 10:54 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
2020-12-06 12:20 ` Eli Zaretskii
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=ab6f6667-4114-4352-ad83-4d677d42934b@default \
--to=drew.adams@oracle.com \
--cc=boruch_baum@gmx.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
--cc=yuri.v.khan@gmail.com \
/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).