From: Michael Heerdegen <michael_heerdegen@web.de>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 22457@debbugs.gnu.org
Subject: bug#22457: 24.5; [PATCH] `dired-mark-if' should not count non-changes
Date: Wed, 26 Jun 2019 00:47:00 +0200 [thread overview]
Message-ID: <87o92lmgez.fsf@web.de> (raw)
In-Reply-To: <m3imst655q.fsf@gnus.org> (Lars Ingebrigtsen's message of "Tue, 25 Jun 2019 17:44:33 +0200")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> --
> *** The marking commands now report how many files were marked by the
> command itself, not how many files are marked in total.
> --
I don't think this exactly describes what the patch changed: it is not
about new vs total marks, but about marks of files that were already
marked before, right?
> Perhaps somebody will want to weigh in here; feel free to revert the
> commit if this is felt to be a confusing change.
IIUC: Maybe we could add to the summary message something like
"(N already were marked)" or so if a command finds existent marks on files
to be marked? That might be useful information, even independent from
this change, because it might also be a hint for a pilot error.
Michael.
next prev parent reply other threads:[~2019-06-25 22:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-24 18:05 bug#22457: 24.5; [PATCH] `dired-mark-if' should not count non-changes Drew Adams
2019-06-25 14:42 ` Lars Ingebrigtsen
2019-06-25 15:33 ` Drew Adams
2019-06-25 15:44 ` Lars Ingebrigtsen
2019-06-25 22:47 ` Michael Heerdegen [this message]
2019-06-25 22:53 ` Lars Ingebrigtsen
2019-06-25 23:02 ` Michael Heerdegen
2019-06-25 23:12 ` Lars Ingebrigtsen
2019-06-25 23:26 ` Drew Adams
2019-06-25 23:30 ` Michael Heerdegen
2019-06-26 0:00 ` Drew Adams
2019-06-26 8:50 ` Andreas Schwab
2019-06-26 13:32 ` Drew Adams
2019-06-25 23:17 ` Drew Adams
2019-06-25 23:28 ` Michael Heerdegen
2019-06-25 15:46 ` Lars Ingebrigtsen
2019-06-25 16:06 ` Drew Adams
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=87o92lmgez.fsf@web.de \
--to=michael_heerdegen@web.de \
--cc=22457@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 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).