From: Juri Linkov <juri@linkov.net>
To: Marcin Borkowski <mbork@mbork.pl>
Cc: Tino Calancha <f92capac@gmail.com>,
Lars Ingebrigtsen <larsi@gnus.org>,
22829@debbugs.gnu.org
Subject: bug#22829: Acknowledgement (25.1.50; Display number of marked files)
Date: Thu, 03 Mar 2016 02:17:23 +0200 [thread overview]
Message-ID: <878u208lf0.fsf@mail.linkov.net> (raw)
In-Reply-To: <878u20abot.fsf@mbork.pl> (Marcin Borkowski's message of "Wed, 02 Mar 2016 21:04:34 +0100")
>>> I confirm this is very useful. I'm using the same for a long time,
>>> but additionally also displaying a total sum of sizes on every mark
>>> (this emulates the behavior of File Commanders on marking files by INS).
>>
>> This is beginning to sound more useful. :-) Including both the number
>> of files and the total file size is something I could see myself wanting
>> to have.
>
> +1.
>
> What about the size of directories are marked? I assume that it is to
> costly to include the recursively computed size...?
Yes, doing `du -sh` often takes soo long... But we could include sizes
of subdirs only when called with a prefix arg. Oh, and I noticed that
the proposed key 'N' is already bound to dired-man in dired-x.el.
Another good mnemonic key would be '#', but it's taken as well.
Than maybe put it on the marking prefix key '*'.
next prev parent reply other threads:[~2016-03-03 0:17 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-27 14:29 bug#22829: 25.1.50; Display number of marked files Tino Calancha
[not found] ` <handler.22829.B.145658318020704.ack@debbugs.gnu.org>
2016-02-27 14:41 ` bug#22829: Acknowledgement (25.1.50; Display number of marked files) Tino Calancha
2016-02-28 5:38 ` Lars Ingebrigtsen
2016-02-28 6:36 ` Tino Calancha
2016-03-02 0:32 ` Juri Linkov
2016-03-02 17:28 ` Lars Ingebrigtsen
2016-03-02 20:04 ` Marcin Borkowski
2016-03-03 0:17 ` Juri Linkov [this message]
2016-03-03 5:52 ` Lars Ingebrigtsen
2016-03-03 11:20 ` Richard Stallman
2016-03-03 11:25 ` Lars Ingebrigtsen
2019-06-25 14:29 ` Lars Ingebrigtsen
2016-03-03 9:58 ` Tino Calancha
2016-03-03 12:27 ` Michael Heerdegen
2016-03-03 12:55 ` Constantino Calancha
2019-06-25 14:29 ` Lars Ingebrigtsen
2016-03-07 0:04 ` Juri Linkov
2016-03-08 10:20 ` Tino Calancha
2016-03-08 0:19 ` Juri Linkov
2016-03-08 10:34 ` Tino Calancha
2016-03-09 16:37 ` Richard Stallman
2016-03-01 11:26 ` bug#22829: 25.1.50; Display number of marked files Constantino Calancha
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=878u208lf0.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=22829@debbugs.gnu.org \
--cc=f92capac@gmail.com \
--cc=larsi@gnus.org \
--cc=mbork@mbork.pl \
/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).