From: Tino Calancha <tino.calancha@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org, Andreas Schwab <schwab@linux-m68k.org>,
tino.calancha@gmail.com
Subject: Re: Dired: Improve symmetry in mark/unmark commands bound to keys
Date: Sun, 25 Sep 2016 04:49:05 +0900 (JST) [thread overview]
Message-ID: <alpine.DEB.2.20.1609250443200.4103@calancha-pc> (raw)
In-Reply-To: <83h995ay04.fsf@gnu.org>
On Sat, 24 Sep 2016, Eli Zaretskii wrote:
>> From: Andreas Schwab <schwab@linux-m68k.org>
>> Date: Sat, 24 Sep 2016 21:31:09 +0200
>> Cc: Emacs developers <emacs-devel@gnu.org>
>>
>> There is no need for dired-mark-or-unmark-extension,
>> dired-mark-extension should to that already. Since the prefix argument
>> has always been useless it is ok to change its meaning, and make it
>> consistent with all other dired commands.
>
> I disagree and object to such a change.
I try to be objective and look at this regardless of my wish. Then, i
cannot see the rationale about what makes special marking by extension.
Why should '* .' prompt for a marker-char (the only guy doing so)
but similar ones as '* @', '* /', or even '% m' should not?
The code is talking us, let's hear what is saying. It should be obvious.
I would be proud on you if you could reconsider your opinion in case
several people here suggest you the opposite. It would be wise.
next prev parent reply other threads:[~2016-09-24 19:49 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-09-24 17:31 Dired: Improve symmetry in mark/unmark commands bound to keys Tino Calancha
2016-09-24 18:12 ` Eli Zaretskii
2016-09-24 18:25 ` Tino Calancha
2016-09-24 19:31 ` Andreas Schwab
2016-09-24 19:39 ` Eli Zaretskii
2016-09-24 19:46 ` Andreas Schwab
2016-09-24 19:58 ` Eli Zaretskii
2016-09-24 20:07 ` Andreas Schwab
2016-09-24 23:49 ` Drew Adams
2016-09-25 9:06 ` Tino Calancha
2016-09-25 18:55 ` John Wiegley
2016-09-26 9:23 ` Tino Calancha
2016-09-26 11:05 ` Tino Calancha
2016-09-26 15:02 ` Eli Zaretskii
2016-09-26 15:06 ` Eli Zaretskii
2016-09-26 15:47 ` John Wiegley
2016-09-26 16:30 ` Tino Calancha
2016-09-26 19:02 ` Eli Zaretskii
2016-10-03 9:21 ` Tino Calancha
2016-10-03 9:54 ` Eli Zaretskii
2016-10-03 11:15 ` Tino Calancha
2016-09-26 21:52 ` John Wiegley
2016-09-25 19:14 ` Eli Zaretskii
2016-09-25 22:43 ` Andreas Schwab
2016-09-25 22:58 ` Andreas Schwab
2016-09-25 23:00 ` Andreas Schwab
2016-09-26 2:38 ` Eli Zaretskii
2016-09-26 8:33 ` Andreas Schwab
2016-09-26 14:59 ` Eli Zaretskii
2016-09-24 19:49 ` Tino Calancha [this message]
[not found] <<alpine.DEB.2.20.1609250230400.4103@calancha-pc>
[not found] ` <<83oa3db20a.fsf@gnu.org>
2016-09-24 18:53 ` 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=alpine.DEB.2.20.1609250443200.4103@calancha-pc \
--to=tino.calancha@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).