From: Devon Sean McCullough <Emacs-Hacker2015@jovi.net>
To: Glenn Morris <rgm@gnu.org>
Cc: 21637@debbugs.gnu.org
Subject: bug#21637: Subject: 24.5; dired-do-compress
Date: Wed, 7 Oct 2015 21:22:56 +0100 [thread overview]
Message-ID: <81B0FFD2-44BE-41DD-9BD0-75BFBC86164D@jovi.net> (raw)
In-Reply-To: <rhegh8exyk.fsf@fencepost.gnu.org>
Ask yourself, what would a reasonable user expect?
If “beyond the scope” means “we don't fix problems” well,
yes, times have changed since I was a paid Emacs maintainer.
My answer would’ve been more of the form, hmm… what's the right thing?
When foo.zip contains only names of the form foo/* perhaps ask
Uncompress foo.zip into directory foo? (y or n)
of course if foo already exists, get confirmation before writing to it
and prompt for an alternative directory name if necessary.
Given one of those archives that would spam the containing directory
(I’ve read ancient religious debates on the topic but no matter)
simply derive a directory name from the archive name.
In the case of a one-file archive, just unpack it
making sure to mention the unpacked name.
Peace
—Devon
P.S. Obviously foo.tar would be treated likewise.
On Oct 6, 2015, at 5:57 PM, Glenn Morris <rgm@gnu.org> wrote:
> Devon Sean McCullough wrote:
>> dired-do-compress does foo.zip --> foo.zip.gz, should do foo.zip -->
>> foo instead.
> "Uncompressing" a zip file may (and normally does?) result in multiple
> output files, which is beyond the scope of dired-do-compress,
> in the same way that it does not extract .tar files.
next prev parent reply other threads:[~2015-10-07 20:22 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-06 15:13 bug#21637: Subject: 24.5; dired-do-compress Devon Sean McCullough
2015-10-06 16:57 ` Glenn Morris
2015-10-07 20:22 ` Devon Sean McCullough [this message]
2015-10-07 20:56 ` Ken Brown
2015-10-07 22:48 ` Devon Sean McCullough
2021-12-02 9:12 ` bug#21637: dired-do-compress and zip files Lars Ingebrigtsen
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=81B0FFD2-44BE-41DD-9BD0-75BFBC86164D@jovi.net \
--to=emacs-hacker2015@jovi.net \
--cc=21637@debbugs.gnu.org \
--cc=rgm@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 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.