From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: schwab@linux-m68k.org, 24518@debbugs.gnu.org
Subject: bug#24518: 25.2.50; dired-mark-extension with prefix arg fails
Date: Sat, 24 Sep 2016 20:39:43 +0300 [thread overview]
Message-ID: <83r389b3j4.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1609250206000.4103@calancha-pc> (message from Tino Calancha on Sun, 25 Sep 2016 02:14:14 +0900 (JST))
> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Sun, 25 Sep 2016 02:14:14 +0900 (JST)
> cc: Andreas Schwab <schwab@linux-m68k.org>, tino.calancha@gmail.com,
> 24518@debbugs.gnu.org
>
> > I believe my recent commit fixed all of the above
> Yeah, you fixed something, and we are exactly in the same point
> that before fixing such thing. We didn't get something better.
We don't have this command signal an error anymore, do we? I think
that's a definite improvement.
Besides, you yourself told me to fix the bug, so I did.
> The point here is that a Dired user would expect/wish that the
> interactive call behaves differently. I do.
> Do you know how i noticed the bug?
> Because i assumed that a prefix argument will unmark as other
> Dired marks, and i got an error (!).
But it isn't true that every Dired command that marks files will
unmark them if invoked with an argument. E.g., dired-mark doesn't.
So this doesn't look like a universal convention in Dired, only a
frequent feature.
OTOH, since Dired allows the user to use different marker characters
in other places, IMO it is not very reasonable to exempt this
particular command. Especially since it did have a (semi-broken) way
of doing that.
next prev parent reply other threads:[~2016-09-24 17:39 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-23 14:13 bug#24518: 25.2.50; dired-mark-extension with prefix arg fails Tino Calancha
2016-09-24 11:52 ` Eli Zaretskii
2016-09-24 12:30 ` Tino Calancha
2016-09-24 12:53 ` Eli Zaretskii
2016-09-24 13:02 ` Tino Calancha
2016-09-24 13:49 ` Eli Zaretskii
2016-09-24 13:15 ` Andreas Schwab
2016-09-24 13:51 ` Eli Zaretskii
2016-09-24 14:06 ` Tino Calancha
2016-09-24 15:11 ` Eli Zaretskii
2016-09-24 16:48 ` Andreas Schwab
2016-09-24 16:58 ` Eli Zaretskii
2016-09-24 17:14 ` Tino Calancha
2016-09-24 17:39 ` Eli Zaretskii [this message]
2016-09-24 17:49 ` Tino Calancha
2016-09-24 19:23 ` Andreas Schwab
2016-09-24 19:13 ` Andreas Schwab
2016-09-24 19:29 ` Eli Zaretskii
2016-09-24 19:41 ` Andreas Schwab
2016-09-25 18:34 ` John Wiegley
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=83r389b3j4.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=24518@debbugs.gnu.org \
--cc=schwab@linux-m68k.org \
--cc=tino.calancha@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 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.