From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Tino Calancha <tino.calancha@gmail.com>
Cc: emacs-devel@gnu.org
Subject: RE: Dired: Improve symmetry in mark/unmark commands bound to keys
Date: Sat, 24 Sep 2016 11:53:07 -0700 (PDT) [thread overview]
Message-ID: <29510b6b-a38d-4abf-b3b4-f5d6f82fd098@default> (raw)
In-Reply-To: <<83oa3db20a.fsf@gnu.org>>
> > I) Add optional argument in 6) unflag-p to behave as the others.
> > II) Add a new command `dired-mark-or-unmark-extension', as
> > `dired-mark-extension' but, in interactive calls:
> > * A prefix argument _unmark_ files.
> > I propose to rebind '* .' to this command instead of the
> > `dired-mark-extension'.
> > After I) and II) we have an uniform behaviour for all
> > commands marking files which are bound to keys. Powerful and easy
> > to remember.
>
> I'm okay with that proposal, but please leave the "* ." key sequence
> at its present binding. For the new dired-mark-or-unmark-extension
> command, I can propose "* e" or "* x", which are not yet taken, both
> of them mnemonically resembling "EXtension".
FWIW, I favor Tino's proposal, including having `* .' UNmark
with a prefix arg (just like the other `*' commands).
I see no special reason why a prefix arg to `* .' would read
the character to use for marking, instead of having it unmark
as proposed.
(FWIW, In Dired+ `* .' has long been bound to a command that
does what Tino proposes. I've never heard a complaint.)
A prefix arg for `* .' currently is not useful, IMO, and
likely never used. It marks the files using a character that
you specify.
Instead, users can use `* c' to change the mark character for
the marked files, however they were marked - very useful.
The ability to have a different mark character has nothing
special to do with marking files by their extension. There
are lots of uses of different mark chars. I've never heard
of _anyone_ taking advantage of the vanilla `* .' prefix arg
behavior to use a different mark character while marking a
given extension.
In fact, my impression is that there are very few Emacs users
who even know about `* c', or know that you can have different
marks and how you can put them to use. See this bug thread,
for example: http://debbugs.gnu.org/cgi/bugreport.cgi?bug=21746#8
next parent reply other threads:[~2016-09-24 18:53 UTC|newest]
Thread overview: 31+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <<alpine.DEB.2.20.1609250230400.4103@calancha-pc>
[not found] ` <<83oa3db20a.fsf@gnu.org>
2016-09-24 18:53 ` Drew Adams [this message]
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
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=29510b6b-a38d-4abf-b3b4-f5d6f82fd098@default \
--to=drew.adams@oracle.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@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).