From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Tino Calancha <tino.calancha@gmail.com>
Cc: tzz@lifelogs.com, 24150@debbugs.gnu.org, clement.pit@gmail.com,
sdl.web@gmail.com
Subject: bug#24150: 26.0.50; New command: dired-create-empty-file
Date: Mon, 3 Jul 2017 08:12:07 -0700 (PDT) [thread overview]
Message-ID: <4467d3df-db36-49fb-8a6b-1014f0d55c18@default> (raw)
In-Reply-To: <83y3s5oaxo.fsf@gnu.org>
> But I don't think M-+ or whatever we bind that command to...
If possible, please do not bind `M-+' to anything in Dired mode.
Dired+ binds `M-+' as a prefix key, for operations on marked
files and dirs gathered recursively from marked subdirs, across
all Dired buffers.
It has been in use for at least 5 years. I think Tino is aware
of this, but I'm not sure.
Again, just a request.
FYI, these are the Dired-mode keys bound on prefix-key `M-+':
M-+ C-t Prefix Command
M-+ C-t c diredp-image-dired-comment-files-recursive
M-+ C-t d diredp-image-dired-display-thumbs-recursive
M-+ C-t r diredp-image-dired-delete-tag-recursive
M-+ C-t t diredp-image-dired-tag-files-recursive
M-+ ! diredp-do-shell-command-recursive
M-+ % Prefix Command
M-+ % c diredp-capitalize-recursive
M-+ % l diredp-downcase-recursive
M-+ % m diredp-mark-files-regexp-recursive
M-+ % u diredp-upcase-recursive
M-+ & diredp-do-async-shell-command-recursive
M-+ * Prefix Command
M-+ * % diredp-mark-files-regexp-recursive
M-+ * * diredp-mark-executables-recursive
M-+ * . diredp-mark-extension-recursive
M-+ * / diredp-mark-directories-recursive
M-+ * @ diredp-mark-symlinks-recursive
M-+ * B diredp-mark-autofiles-recursive
M-+ : Prefix Command
M-+ : d diredp-do-decrypt-recursive
M-+ : e diredp-do-encrypt-recursive
M-+ : s diredp-do-sign-recursive
M-+ : v diredp-do-verify-recursive
M-+ @ diredp-do-apply-function-recursive
M-+ A diredp-do-search-recursive
M-+ C diredp-do-copy-recursive
M-+ D diredp-do-delete-recursive
M-+ F diredp-do-find-marked-files-recursive
M-+ H diredp-do-hardlink-recursive
M-+ M diredp-do-chmod-recursive
M-+ P diredp-do-print-recursive
M-+ Q diredp-do-query-replace-regexp-recursive
M-+ R diredp-do-move-recursive
M-+ S diredp-do-symlink-recursive
M-+ Y diredp-do-relsymlink-recursive
next prev parent reply other threads:[~2017-07-03 15:12 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-04 13:25 bug#24150: 25.1.50; New command: dired-create-empty-file Tino Calancha
2016-08-04 13:54 ` Clément Pit--Claudel
2016-08-04 16:29 ` Leo Liu
2016-08-04 17:13 ` Ted Zlatanov
2016-08-04 17:29 ` Drew Adams
2016-08-05 6:03 ` Tino Calancha
2016-08-05 14:48 ` Drew Adams
2016-08-06 12:38 ` Tino Calancha
2016-08-05 6:07 ` Tino Calancha
2017-05-03 8:23 ` Tino Calancha
2017-07-03 4:51 ` bug#24150: 26.0.50; " Tino Calancha
2017-07-03 14:24 ` Eli Zaretskii
2017-07-03 15:04 ` Tino Calancha
2017-07-03 16:33 ` Eli Zaretskii
2017-07-03 20:18 ` Thien-Thi Nguyen
2017-07-07 13:13 ` Ted Zlatanov
2017-07-07 13:17 ` Drew Adams
2017-07-07 13:31 ` Ted Zlatanov
2017-07-03 15:12 ` Drew Adams [this message]
2017-07-05 18:28 ` Eli Zaretskii
2017-07-05 19:34 ` Drew Adams
2017-07-07 5:36 ` Tino Calancha
2017-07-07 11:11 ` Drew Adams
2018-07-10 7:01 ` Tino Calancha
2018-07-10 7:42 ` Phil Sainty
2018-07-17 7:39 ` Tino Calancha
2018-07-20 9:03 ` Eli Zaretskii
2018-07-23 3:57 ` Tino Calancha
2018-07-27 8:39 ` Eli Zaretskii
2018-07-31 4:47 ` Tino Calancha
2018-07-31 16:20 ` Eli Zaretskii
2018-08-01 5:16 ` Tino Calancha
2018-08-01 6:24 ` Eli Zaretskii
2018-08-01 7:13 ` Tino Calancha
2018-08-01 8:56 ` Eli Zaretskii
2018-08-01 9:31 ` Tino Calancha
2018-08-01 11:45 ` Eli Zaretskii
2018-08-02 4:34 ` 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=4467d3df-db36-49fb-8a6b-1014f0d55c18@default \
--to=drew.adams@oracle.com \
--cc=24150@debbugs.gnu.org \
--cc=clement.pit@gmail.com \
--cc=eliz@gnu.org \
--cc=sdl.web@gmail.com \
--cc=tino.calancha@gmail.com \
--cc=tzz@lifelogs.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).