From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tino.calancha@gmail.com, Andreas Schwab <schwab@linux-m68k.org>,
24518@debbugs.gnu.org
Subject: bug#24518: 25.2.50; dired-mark-extension with prefix arg fails
Date: Sun, 25 Sep 2016 02:14:14 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1609250206000.4103@calancha-pc> (raw)
In-Reply-To: <83vaxlb5ge.fsf@gnu.org>
On Sat, 24 Sep 2016, Eli Zaretskii wrote:
>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Cc: tino.calancha@gmail.com, 24518@debbugs.gnu.org
>> Date: Sat, 24 Sep 2016 18:48:35 +0200
>>
>>> Like I said: it looks a kludge, but it definitely isn't an accident.
>>
>> What makes you that confident? It look certainly like a
>> misunderstanding.
>>
>>> I suggested to replace 'P' with 'c' in the interactive spec, to make
>>> it less kludgey.
>>
>> "c" would make it non-optional, definitely not intented.
>>
>>>> That doesn't look like this was an intented feature (being
>>>> undocumented).
>>>
>>> It's documented, see the doc string.
>>
>> It isn't. There is no occurence of "prefix" in the doc string.
>
> 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.
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 (!).
The right thing here is to unmark with a prefix argument: other thing than
that would be unconsistent. Not Dired style, and pretty useless.
For me its not a problem, because i use Dired+. Other people are not as
lucky.
next prev parent reply other threads:[~2016-09-24 17:14 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 [this message]
2016-09-24 17:39 ` Eli Zaretskii
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
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=alpine.DEB.2.20.1609250206000.4103@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=24518@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=schwab@linux-m68k.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).