From: Drew Adams <drew.adams@oracle.com>
To: Juri Linkov <juri@linkov.net>
Cc: Richard Stallman <rms@gnu.org>,
mattiase@acm.org, jidanni@jidanni.org, stefankangas@gmail.com,
larsi@gnus.org, 44273@debbugs.gnu.org
Subject: bug#44273: "total used in directory 19 available 5.2 GiB"
Date: Tue, 3 Nov 2020 11:51:59 -0800 (PST) [thread overview]
Message-ID: <4752bd8e-2361-48b8-aca1-3c94f84ea7d3@default> (raw)
In-Reply-To: <87v9emomvm.fsf@mail.linkov.net>
> > 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):
>
> And maybe also show the number of marked/flagged files,
> updated on every marking/unmarking.
IMO, that's better done in the mode line, which is what
Dired+ does.
The "total" line we're talking about, for each subdir
listing, shows the # of visible files for that subdir
listing and the total # of files in the top-level dir
of the buffer.
The mode line shows Dired/date or Dired/name, and the
# of marks (*) and # of flags (D). And it shows the
ordinal # of the file or dir on the current line (point),
with the current sorting, as well as the total number of
files/dirs for that subdir listing.
next prev parent reply other threads:[~2020-11-03 19:51 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
2020-11-03 18:39 ` Juri Linkov
2020-11-03 19:51 ` Drew Adams [this message]
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
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=4752bd8e-2361-48b8-aca1-3c94f84ea7d3@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 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).