From: Drew Adams <drew.adams@oracle.com>
To: Stefan Monnier <monnier@iro.umontreal.ca>, emacs-devel@gnu.org
Subject: RE: [found the culprit]
Date: Wed, 14 Nov 2018 09:22:59 -0800 (PST) [thread overview]
Message-ID: <ec844ced-b7ef-41fa-9b7e-433397993823@default> (raw)
In-Reply-To: <jwvsh031ugt.fsf-monnier+gmane.emacs.devel@gnu.org>
> >> Compress or uncompress marked (or next prefix argument) files.
> >> A prefix argument ARG specifies files to use instead of marked.
> >> An integer means use the next ARG files (previous -ARG, if < 0).
> >> `C-u': Use the current file (whether or not any are marked).
> >> `C-u C-u': Use all files in Dired, except directories.
> >> `C-u C-u C-u': Use all files and directories, except `.' and `..'.
> >> `C-u C-u C-u C-u': Use all files and all directories.
> >
> > Is "C-u 0' available?
>
> I don't think we should base our decision on what some external package
> happened to choose. Especially since the above C-u usage does not
> follow Emacs's use of C-u.
1. I didn't say you should base your decision on what Dired+
uses. I just mentioned what it uses, and has used for a
long time. And it's a general scheme, applied to `dired-do-*'
commands generally. The conflict is not a minor one, e.g.,
affecting just `Z'.
A better idea is for vanilla Emacs to adopt that general
scheme. It's a good scheme - I didn't just "happen to
choose" it. And it fits with the existing vanilla behavior,
both wrt numeric arg and plain C-u. The only divergence is
the addition of behaviors for multiple C-u, which most users
will use much less commonly. (Well, actually, I find I use
multiple C-u more than I use numeric.)
2. How does the above C-u usage "not follow Emacs's use of C-u"?
3. `Z' is a `dired-do-*' command. Its prefix arg behavior
should, other things being equal, follow the pattern of
the other `dired-do-*' commands.
However, the behavior of `Z' itself (`dired-do-compress')
can be whatever you want, including treating directories
specially.
next prev parent reply other threads:[~2018-11-14 17:22 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-13 13:18 tgz extension and dired-do-compress Uwe Brauer
2018-11-13 17:31 ` Eli Zaretskii
2018-11-13 18:15 ` Uwe Brauer
2018-11-14 12:07 ` [emacs -q versus empty .emacs file] (was: tgz extension and dired-do-compress) Uwe Brauer
2018-11-14 12:12 ` [found the culprit] (was: [emacs -q versus empty .emacs file]) Uwe Brauer
2018-11-14 13:15 ` Noam Postavsky
2018-11-14 13:50 ` [found the culprit] Uwe Brauer
2018-11-14 15:43 ` [found the culprit] (was: [emacs -q versus empty .emacs file]) Eli Zaretskii
2018-11-14 15:49 ` [found the culprit] Uwe Brauer
2018-11-14 16:09 ` Eli Zaretskii
2018-11-14 16:39 ` Stefan Monnier
2018-11-14 16:57 ` Uwe Brauer
2018-11-14 17:31 ` Drew Adams
2018-11-14 18:20 ` Stefan Monnier
2018-11-14 19:58 ` Drew Adams
2018-11-14 20:24 ` Eli Zaretskii
2018-11-14 20:43 ` Stefan Monnier
2018-11-14 19:59 ` Eli Zaretskii
2018-11-14 20:38 ` Stefan Monnier
2018-11-14 21:01 ` jpff
2018-11-16 6:45 ` Van L
2018-11-16 0:51 ` [found the culprit] (was: [emacs -q versus empty .emacs file]) Richard Stallman
2018-11-14 12:21 ` [emacs -q versus empty .emacs file] (was: tgz extension and dired-do-compress) Alan Mackenzie
2018-11-14 13:16 ` [emacs -q versus empty .emacs file] Uwe Brauer
[not found] ` <<87tvkjq2mh.fsf_-_@mat.ucm.es>
[not found] ` <<834lcj8y1f.fsf@gnu.org>
2018-11-14 16:17 ` [found the culprit] (was: [emacs -q versus empty .emacs file]) Drew Adams
2018-11-14 16:37 ` Eli Zaretskii
2018-11-14 16:48 ` [found the culprit] Stefan Monnier
2018-11-14 17:22 ` Drew Adams [this message]
2018-11-14 18:03 ` Stefan Monnier
2018-11-14 19:40 ` Drew Adams
2018-11-14 20:33 ` Davis Herring
2018-11-14 21:21 ` Drew Adams
2018-11-15 2:34 ` Mike Kupfer
2018-11-16 0:55 ` Richard Stallman
2018-11-16 2:24 ` Clément Pit-Claudel
2018-11-16 7:48 ` Eli Zaretskii
2018-11-16 13:04 ` Stefan Monnier
2018-11-16 22:59 ` Richard Stallman
2018-11-16 16:17 ` Drew Adams
2018-11-16 23:01 ` Richard Stallman
2018-11-17 8:04 ` Yuri Khan
2018-11-18 0:24 ` Richard Stallman
2018-11-17 1:05 ` Clément Pit-Claudel
2018-11-16 23:01 ` Richard Stallman
2018-11-17 7:42 ` Yuri Khan
2018-11-15 4:57 ` [found the culprit] (was: [emacs -q versus empty .emacs file]) Yuri Khan
2018-11-15 9:46 ` [found the culprit] Andreas Schwab
2018-11-15 15:21 ` Yuri Khan
[not found] ` <<<87tvkjq2mh.fsf_-_@mat.ucm.es>
[not found] ` <<<834lcj8y1f.fsf@gnu.org>
[not found] ` <<f0a3a374-d8ac-45b6-8de6-0e8ccc0ea696@default>
[not found] ` <<83y39v7gym.fsf@gnu.org>
2018-11-14 17:10 ` [found the culprit] (was: [emacs -q versus empty .emacs file]) Drew Adams
[not found] <<875zx1xgiq.fsf@mat.ucm.es>
[not found] <<<875zx1xgiq.fsf@mat.ucm.es>
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=ec844ced-b7ef-41fa-9b7e-433397993823@default \
--to=drew.adams@oracle.com \
--cc=emacs-devel@gnu.org \
--cc=monnier@iro.umontreal.ca \
/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).