all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Oleh Krehel <ohwoeowho@gmail.com>
To: Juri Linkov <juri@linkov.net>
Cc: Eli Zaretskii <eliz@gnu.org>, emacs-devel@gnu.org
Subject: Re: master 6d6bf46 2/2: Make dired-do-compress work for *.tar.gz files
Date: Wed, 21 Oct 2015 10:00:08 +0200	[thread overview]
Message-ID: <874mhktzw7.fsf@gmail.com> (raw)
In-Reply-To: <87mvvdyx0i.fsf@mail.linkov.net> (Juri Linkov's message of "Wed,  21 Oct 2015 01:51:11 +0300")

Juri Linkov <juri@linkov.net> writes:

>> I also want to add a new command to dired that compresses all marked
>> files into a single named archive: the user gets prompted for a name
>> (through `completing-read'+`read-file-name-internal') and the shell
>> command is resolved from that name. I'd like for it to be bound by
>> default, like "Z". Maybe like this:
>>
>>     (define-key map "c" 'dired-compress)
>>
>> The proposed key isn't bound by default. Is that OK?
>
> Aren't upper-case Dired keys reserved for potentially dangerous commands
> because upper-case keys are harder to press (require holding Shift-key).
> I guess if your command will ask additional information from the minibuffer
> then either lower-case "c" or "z" are fine because they won't run immediately.
> "Z" would be good too if you could improve it in a backward-compatible way.

I don't think it's possible to extend "Z", unless it's with a prefix arg
or something, just because it already has a very different behavior for
a group of marked files.

Pressing something like "c" or "z" is much shorter than "C-u Z". And the
logic is different anyway.



  reply	other threads:[~2015-10-21  8:00 UTC|newest]

Thread overview: 29+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <20151013135354.28594.43074@vcs.savannah.gnu.org>
     [not found] ` <E1Zm01b-0007SW-BB@vcs.savannah.gnu.org>
2015-10-13 18:28   ` master 6d6bf46 2/2: Make dired-do-compress work for *.tar.gz files Glenn Morris
2015-10-13 18:38     ` Paul Eggert
2015-10-14  7:58       ` Oleh Krehel
2015-10-14 15:17         ` Paul Eggert
2015-10-14  7:56     ` Oleh Krehel
2015-10-14 16:16       ` Eli Zaretskii
2015-10-14 18:51         ` Achim Gratz
2015-10-14 19:02           ` Eli Zaretskii
2015-10-15 13:07           ` Oleh Krehel
2015-10-15 15:55             ` Eli Zaretskii
2015-10-15 19:46             ` Achim Gratz
2015-10-15 16:48       ` Glenn Morris
2015-10-15 17:06         ` Eli Zaretskii
2015-10-16 10:44           ` Oleh Krehel
2015-10-16 13:23             ` Eli Zaretskii
2015-10-16 13:47               ` Oleh Krehel
2015-10-16 14:35                 ` Eli Zaretskii
2015-10-20  8:59                   ` Oleh Krehel
2015-10-20 14:57                     ` Eli Zaretskii
2015-10-21  7:57                       ` Oleh Krehel
2015-10-21 15:04                       ` Oleh Krehel
2015-10-21 16:28                         ` Eli Zaretskii
2015-10-22 10:59                           ` Oleh Krehel
2015-10-20 22:51                     ` Juri Linkov
2015-10-21  8:00                       ` Oleh Krehel [this message]
2015-10-16 15:35               ` Paul Eggert
2015-10-16 16:11                 ` Eli Zaretskii
2015-10-16 16:26             ` Glenn Morris
2015-10-16 12:11         ` Oleh Krehel

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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=874mhktzw7.fsf@gmail.com \
    --to=ohwoeowho@gmail.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=juri@linkov.net \
    /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 external index

	https://git.savannah.gnu.org/cgit/emacs.git
	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.