From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>, Richard Stallman <rms@gnu.org>
Cc: mattiase@acm.org, larsi@gnus.org, jidanni@jidanni.org,
stefankangas@gmail.com, 44273@debbugs.gnu.org
Subject: bug#44273: "total used in directory 19 available 5.2 GiB"
Date: Mon, 2 Nov 2020 19:17:07 -0800 (PST) [thread overview]
Message-ID: <136f5a4f-78ff-4e2a-965f-56eec3350804@default> (raw)
In-Reply-To: <89ab11be-72d6-45a9-a4a6-f63134636a44@default>
> > Maybe it could help to show some explanation with tooltips
> > over cryptic parts of that line.
>
> FWIW:
>
> In my library ls-lisp+.el I use tooltips and links on
> parts of that line, and the text for that line is a
> bit different. E.g.:
>
> files 1610/1610 space used 116754 available 101631612
>
> There are two parts, with a tooltip each:
>
> 1. files 1610/1610
> 2. space used 116754 available 101631612
>
> Tooltip for #1:
> Files shown / total files in directory [RET, mouse-2: more info]
>
> Tooltip for #2:
> Kbytes used in directory, Kbytes available on disk [RET, mouse-2: more info]
>
> Each part also has a link, which shows *Help* with
> the `file-attributes' for the directory in tabular form.
FWIW, looking for something else I came across this
emacs-develpost from 2016, which also talks about
"files N/M", i.e., showing the number of files that
are currently listed and the total number of files
(including hidden/omitted):
https://lists.gnu.org/archive/html/emacs-devel/2016-09/msg00277.html
next prev parent reply other threads:[~2020-11-03 3:17 UTC|newest]
Thread overview: 68+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-28 5:12 bug#44273: "total used in directory 19 available 5.2 GiB" 積丹尼 Dan Jacobson
2020-10-28 10:37 ` Mattias Engdegård
2020-10-28 10:43 ` Lars Ingebrigtsen
2020-10-28 10:53 ` Mattias Engdegård
2020-10-28 11:02 ` Lars Ingebrigtsen
2020-10-28 11:18 ` Mattias Engdegård
2020-10-28 11:23 ` Lars Ingebrigtsen
2020-10-28 11:47 ` Andreas Schwab
2020-10-28 12:10 ` Lars Ingebrigtsen
2020-10-28 12:18 ` Mattias Engdegård
2020-10-28 12:26 ` Andreas Schwab
2020-10-28 12:29 ` Lars Ingebrigtsen
2020-10-28 15:38 ` Eli Zaretskii
2020-10-28 15:34 ` Eli Zaretskii
2020-10-29 8:36 ` Michael Albinus
2020-10-28 14:39 ` Drew Adams
2020-10-28 14:49 ` Mattias Engdegård
2020-10-28 15:28 ` Eli Zaretskii
2020-10-30 11:36 ` Lars Ingebrigtsen
2020-10-30 11:41 ` Eli Zaretskii
2020-10-31 9:44 ` Eli Zaretskii
2020-10-28 15:19 ` Eli Zaretskii
2020-10-28 15:55 ` Stefan Kangas
2020-10-28 15:59 ` Eli Zaretskii
2020-10-29 0:03 ` Stefan Kangas
2020-10-29 3:34 ` Eli Zaretskii
2020-10-29 8:48 ` Andreas Schwab
2020-10-30 3:05 ` Richard Stallman
2020-10-30 7:18 ` Juri Linkov
2020-10-30 8:17 ` Eli Zaretskii
2020-10-30 11:33 ` Lars Ingebrigtsen
2020-10-30 11:39 ` Eli Zaretskii
2020-10-30 11:41 ` Lars Ingebrigtsen
2020-10-30 11:49 ` Eli Zaretskii
2020-11-01 11:33 ` Lars Ingebrigtsen
2020-10-31 19:14 ` Juri Linkov
2020-11-01 11:38 ` Lars Ingebrigtsen
2020-11-01 11:55 ` Mattias Engdegård
2020-11-01 15:21 ` Eli Zaretskii
2020-11-01 15:41 ` Mattias Engdegård
2020-11-01 15:51 ` Eli Zaretskii
2020-11-01 16:37 ` Mattias Engdegård
2020-11-01 19:25 ` Jean Louis
2021-10-11 12:35 ` Stefan Kangas
2020-11-01 19:16 ` Jean Louis
2020-11-01 18:57 ` Jean Louis
2020-11-01 19:33 ` Eli Zaretskii
2020-11-01 19:38 ` 積丹尼 Dan Jacobson
2020-11-01 19:43 ` Eli Zaretskii
2020-11-01 19:51 ` 積丹尼 Dan Jacobson
2020-10-31 4:47 ` Richard Stallman
2020-10-30 19:03 ` Drew Adams
2020-11-03 3:17 ` Drew Adams [this message]
2020-11-03 18:39 ` Juri Linkov
2020-11-03 19:51 ` Drew Adams
2020-11-04 19:41 ` Juri Linkov
2020-11-04 20:53 ` Drew Adams
2020-10-30 11:34 ` Lars Ingebrigtsen
2020-10-29 4:54 ` Richard Stallman
2020-10-30 12:22 ` Lars Ingebrigtsen
2020-10-30 12:25 ` Eli Zaretskii
2020-10-30 13:39 ` Michael Albinus
2020-10-30 13:46 ` Eli Zaretskii
2020-10-30 14:54 ` Michael Albinus
2020-10-31 0:12 ` 積丹尼 Dan Jacobson
2020-10-31 4:45 ` Richard Stallman
2020-10-31 4:47 ` Richard Stallman
2020-10-31 4:47 ` Richard Stallman
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=136f5a4f-78ff-4e2a-965f-56eec3350804@default \
--to=drew.adams@oracle.com \
--cc=44273@debbugs.gnu.org \
--cc=jidanni@jidanni.org \
--cc=juri@linkov.net \
--cc=larsi@gnus.org \
--cc=mattiase@acm.org \
--cc=rms@gnu.org \
--cc=stefankangas@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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.