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 11:58:28 -0800 (PST) [thread overview]
Message-ID: <6d51f735-30f2-4310-b9b3-7300241c4a21@default> (raw)
In-Reply-To: <jwvwopfzg9n.fsf-monnier+gmane.emacs.devel@gnu.org>
> The question is not "what do we do when we receive an uncompressed tar
> file", but rather "what do we do when we have a compressed tar file"
> and "what do we do when the user requests to compress a directory".
`Z' should do what it's long done.
But if you want to give it a special behavior for
directories, I have no objection. I already said
that the particular command can have behavior that
treats exceptions exceptionally. The exception
is for directories - we should not change the whole
`Z' command for all tar and tar.gz just because we
want to do something special in the case of directories.
As for the behavior that you want - the new `Z'
behavior: just define it as a new, different command.
Give it another key, if you think that's needed.
I don't see why the general behavior of `Z' should
be changed for tar/tar.gz/.tgz, just because of the
desire to do something better for directories.
> in my experience ".tar.gz" is itself considered as an
> archive format rather
> than "a compressed file which contains an archive"
Fair enough. But that's not the only way it's
considered, I think. It is still possible, at
least outside Dired, to uncompress without extracting,
right?
> in the sense that in the vast majority of cases people
> take a directory and pack it up into a .tar.gz "tarball"
> or take a ".tar.gz" and unpack it into a directory tree:
> the cases where the .tar intermediate step is used
> explicitly are much less frequent.
Yes, though an exception, the directory case is
common. ;-)
It's an exception, in that its only one thing you can
tar up and compress. But you're right that it is
very common.
Maybe we should have a separate command for it?
> > The question is whether `Z' should support tar files.
>
> No. It does and has done so for a long time and there's
> no suggestion to make it stop supporting it.
>
> And indeed Dired's `Z` has been compressing directories to tar.gz and
> uncompressing tar.gz to directories (rather than to tar files) for many
> years now.
So what's new is that it now does the same for
non-directories? If so, why is that good/needed?
Maybe I'm misunderstanding what this is all about.
If so, I'm sorry for all the noise.
next prev parent reply other threads:[~2018-11-14 19:58 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 [this message]
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
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=6d51f735-30f2-4310-b9b3-7300241c4a21@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).