From: Juri Linkov <juri@linkov.net>
To: Tino Calancha <f92capac@gmail.com>
Cc: 22893@debbugs.gnu.org, larsi@gnus.org
Subject: bug#22893: 25.1.50; dired-get-marked-files get all marked
Date: Fri, 11 Mar 2016 02:48:23 +0200 [thread overview]
Message-ID: <871t7heku0.fsf@mail.linkov.net> (raw)
In-Reply-To: <alpine.LRH.2.20.1603101340030.23184@calancha-ilc.kek.jp> (Tino Calancha's message of "Thu, 10 Mar 2016 13:43:43 +0900 (JST)")
> What about `dired-map-over-marks-check' in dired-aux.el?
> Should we make resemble `dired-map-over-marks' in its
> optional arguments?
Does it make sense to add ALL-MARKS to commands that use
`dired-map-over-marks-check', e.g. to compress or byte-compile
files flagged for deletion?
This also raises the question how do you want to use ALL-MARKS
in bug#22829 to display the number of marked files? Shouldn't we
display the numbers separately for files flagged for deletion
(helps to see how much space will free up after deletion),
and marked with the default mark (to see whether the total sizes
of marked files will fit to copy to another file partition)?
Or there is not enough screen space in the echo area to display
statistics separately for every used marker-char?
next prev parent reply other threads:[~2016-03-11 0:48 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-03 9:38 bug#22893: 25.1.50; dired-get-marked-files get all marked Tino Calancha
2016-03-04 12:32 ` Lars Ingebrigtsen
2016-03-05 13:14 ` Tino Calancha
2016-03-08 5:18 ` Tino Calancha
2016-03-08 16:01 ` Eli Zaretskii
2016-03-09 15:27 ` Tino Calancha
2016-03-09 23:57 ` Juri Linkov
2016-03-10 4:19 ` Tino Calancha
2019-06-25 14:07 ` bug#22892: " Lars Ingebrigtsen
2020-08-12 11:58 ` Lars Ingebrigtsen
2016-03-10 4:43 ` Tino Calancha
2016-03-11 0:48 ` Juri Linkov [this message]
2016-03-22 9:31 ` bug#22893: dired-marker-regexp use dired-re-mark Tino 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=871t7heku0.fsf@mail.linkov.net \
--to=juri@linkov.net \
--cc=22893@debbugs.gnu.org \
--cc=f92capac@gmail.com \
--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.