From: John Wiegley <jwiegley@gmail.com>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 24518@debbugs.gnu.org, Richard Stallman <rms@gnu.org>,
tino.calancha@gmail.com
Subject: bug#24518: 25.2.50; dired-mark-extension with prefix arg fails
Date: Sun, 25 Sep 2016 11:34:08 -0700 [thread overview]
Message-ID: <m2k2dzzv4v.fsf@newartisans.com> (raw)
In-Reply-To: <8737kp2ih4.fsf@linux-m68k.org> (Andreas Schwab's message of "Sat, 24 Sep 2016 21:41:43 +0200")
[-- Attachment #1: Type: text/plain, Size: 2269 bytes --]
>>>>> "AS" == Andreas Schwab <schwab@linux-m68k.org> writes:
AS> Yes, it is. It's a misfeature. It makes it alien with all the other dired
AS> commands.
Hello, I'm just joining this conversation, but I've read all the backlog.
First, if Eli believes that maintenance requires retaining a 22 year old
feature -- however improbable its use, however idiosyncratic its behavior when
compared to other dired commands -- that's the end of the discussion here. I
ask that you respect this. You need to convince your maintainer of the merits
of the change, not argue that his decision is without ground. He has all the
ground he needs due to his role on this project.
Do I think it's a wart that should be fixed? Maybe. But we have to tread very
carefully here. We have a commitment to those whom we maintain Emacs for: to
avoid gratuitously changing long-standing behavior without considering every
angle. If we allowed everyone to change whatever annoyed them, just because
they thought it was an improvement, we'd be in a terrible state.
I'd like to see a couple of things happen from here:
1. Begin a discussion on emacs-devel about the behavior of this command.
Solicit the wisdom of other old-timers on that list. Present your case
dispassionately, in terms of what we gain from such a change.
2. Somehow poll our users to find out if, truly, no one uses this command. We
may not find those people -- to date, we've been terrible at effective
polling -- but if we can't find a single person who wants the feature, and
many who want uniformity, at least we have some data to consider.
Calling each other reasonable or unreasonable, or debating this as though it
should "just be obvious" and thus Eli's opinion doesn't matter, is not the way
to make progress. _What he says goes_, because in the end, he controls who is
allowed to commit changes and who isn't.
Let's focus on the technical issues, and broaden the discussion. So far, a
heated debate between three people will never convince me that we need to
change 22 years of prior art, either.
--
John Wiegley GPG fingerprint = 4710 CF98 AF9B 327B B80F
http://newartisans.com 60E1 46C4 BD1A 7AC1 4BA2
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 629 bytes --]
prev parent reply other threads:[~2016-09-25 18:34 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
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 [this message]
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=m2k2dzzv4v.fsf@newartisans.com \
--to=jwiegley@gmail.com \
--cc=24518@debbugs.gnu.org \
--cc=rms@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.