From: Tino Calancha <f92capac@gmail.com>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: Tino Calancha <f92capac@gmail.com>, 22829@debbugs.gnu.org
Subject: bug#22829: Acknowledgement (25.1.50; Display number of marked files)
Date: Sun, 28 Feb 2016 15:36:48 +0900 (JST) [thread overview]
Message-ID: <alpine.LRH.2.20.1602281529080.3831@calancha-ilc.kek.jp> (raw)
In-Reply-To: <87mvqlv1h4.fsf@gnus.org>
> And I'm not sure I'm feeling the utility of this function, either.
> What's the use case?
For those marking files in several directories quite often, and using
dired-change-marks to separate files in different categories: those
people may be interested in counting number of marked files. I need
this every day, but I agree not too many people would find it useful.
next prev parent reply other threads:[~2016-02-28 6:36 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 [this message]
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
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=alpine.LRH.2.20.1602281529080.3831@calancha-ilc.kek.jp \
--to=f92capac@gmail.com \
--cc=22829@debbugs.gnu.org \
--cc=larsi@gnus.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 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.