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


> 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.
People often mark and unmark, but much less people mark with other
marks than ?*.  If they really want that, they still can call the
function non interactively, or use `dired-change-marks'.
Prompting user for the mark character is annoying: 99% of the times i just want
to be asked about the extension
Believe me, using a prefix argument for unmark is very useful.

IMO, my proposal makes a better command:
*) Interactively, this command will handle its optional argument as
    `dired-mark-files-regexp': a prefix argument sets marker-char ?\s, i.e.,
    unmark files.
*) In non interactive calls, the meaning of marker-char is, again, as
    `dired-mark-files-regexp': the character to use for mark the files.

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






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

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.1609242129170.8821@calancha-pc \
    --to=tino.calancha@gmail.com \
    --cc=24518@debbugs.gnu.org \
    --cc=eliz@gnu.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).