unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Tino Calancha <tino.calancha@gmail.com>
Cc: 24518@debbugs.gnu.org
Subject: bug#24518: 25.2.50; dired-mark-extension with prefix arg fails
Date: Sat, 24 Sep 2016 15:53:03 +0300	[thread overview]
Message-ID: <8337kpcvdc.fsf@gnu.org> (raw)
In-Reply-To: <alpine.DEB.2.20.1609242129170.8821@calancha-pc> (message from Tino Calancha on Sat, 24 Sep 2016 21:30:11 +0900 (JST))

> From: Tino Calancha <tino.calancha@gmail.com>
> Date: Sat, 24 Sep 2016 21:30:11 +0900 (JST)
> cc: Tino Calancha <tino.calancha@gmail.com>, 24518@debbugs.gnu.org
> 
> 
> On Sat, 24 Sep 2016, Eli Zaretskii wrote:
> 
> > This loses the feature whereby the user could also specify the
> > character to use as the marker.  Try "C-u 65 * . el RET" to see what
> > that does.
> That feature has never being available since `dired-x' was added to Emacs
> in 1994: the bug came from the very first commit.  No user will miss
> that feature because nobody ever could use it.

??? The example I gave works with the unmodified sources.  When used
as I've shown, there's no bug, and the command does what I expect.  So
how can we be sure no one ever used it that way and won't miss this
optional behavior?

Can you explain your logic here?

> > While using the numeric code of a character sounds like a kludge, the
> > current implementation seems to do that deliberately.  It might make 
> > sense to use 'c' instead of 'P' there, I think, but your patch totally
> > changes the semantics of the prefix argument, so I'm not sure I can 
> > endorse such a change.
> Sure, we could use 'c' and fix it.  We could provide such feature not working
> in >20 years without nobody oppening a bug report.  That sounds like a
> not useful feature at all.

It's an existing feature.  I won't agree to removing features that
existed for the last 22 years without a very good reason.  We have no
good means of finding out whether anyone out there uses this; if
someone does, removing this feature will most probably be a source of
aggravation for them.

> Believe me, using a prefix argument for unmark is very useful.

I believe you.  But we will have to provide this feature without
breaking other existing features.

> For me this uniform behaviour between these two marking commands is
> a very nice thing.

I don't disagree.  I just don't want to break existing features.

Thanks.





  reply	other threads:[~2016-09-24 12:53 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 [this message]
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

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=8337kpcvdc.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=24518@debbugs.gnu.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 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).