From mboxrd@z Thu Jan  1 00:00:00 1970
Path: news.gmane.org!.POSTED!not-for-mail
From: Stefan Monnier <monnier@iro.umontreal.ca>
Newsgroups: gmane.emacs.devel
Subject: Re: [found the culprit]
Date: Wed, 14 Nov 2018 13:20:00 -0500
Message-ID: <jwvwopfzg9n.fsf-monnier+gmane.emacs.devel@gnu.org>
References: <875zx1xgiq.fsf@mat.ucm.es> <83lg5w9956.fsf@gnu.org>
	<87d0r76ewm.fsf_-_@mat.ucm.es> <87tvkjq2mh.fsf_-_@mat.ucm.es>
	<834lcj8y1f.fsf@gnu.org>
	<jwvy39v1usx.fsf-monnier+gmane.emacs.devel@gnu.org>
	<874lcjoauq.fsf@mat.ucm.es>
	<340d2bf9-46b9-4bb3-aea6-0f4dd507b6cd@default>
NNTP-Posting-Host: blaine.gmane.org
Mime-Version: 1.0
Content-Type: text/plain
X-Trace: blaine.gmane.org 1542219507 19793 195.159.176.226 (14 Nov 2018 18:18:27 GMT)
X-Complaints-To: usenet@blaine.gmane.org
NNTP-Posting-Date: Wed, 14 Nov 2018 18:18:27 +0000 (UTC)
User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/27.0.50 (gnu/linux)
To: emacs-devel@gnu.org
Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 14 19:18:23 2018
Return-path: <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Envelope-to: ged-emacs-devel@m.gmane.org
Original-Received: from lists.gnu.org ([208.118.235.17])
	by blaine.gmane.org with esmtp (Exim 4.84_2)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1gMzk5-0004zs-Os
	for ged-emacs-devel@m.gmane.org; Wed, 14 Nov 2018 19:18:21 +0100
Original-Received: from localhost ([::1]:33678 helo=lists.gnu.org)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>)
	id 1gMzmC-0008If-1c
	for ged-emacs-devel@m.gmane.org; Wed, 14 Nov 2018 13:20:32 -0500
Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:51164)
	by lists.gnu.org with esmtp (Exim 4.71)
	(envelope-from <ged-emacs-devel@m.gmane.org>) id 1gMzlt-00087D-GH
	for emacs-devel@gnu.org; Wed, 14 Nov 2018 13:20:14 -0500
Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71)
	(envelope-from <ged-emacs-devel@m.gmane.org>) id 1gMzlp-00011g-PC
	for emacs-devel@gnu.org; Wed, 14 Nov 2018 13:20:13 -0500
Original-Received: from [195.159.176.226] (port=54040 helo=blaine.gmane.org)
	by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16)
	(Exim 4.71) (envelope-from <ged-emacs-devel@m.gmane.org>)
	id 1gMzlp-00010M-F8
	for emacs-devel@gnu.org; Wed, 14 Nov 2018 13:20:09 -0500
Original-Received: from list by blaine.gmane.org with local (Exim 4.84_2)
	(envelope-from <ged-emacs-devel@m.gmane.org>) id 1gMzjg-0004Vu-Tf
	for emacs-devel@gnu.org; Wed, 14 Nov 2018 19:17:56 +0100
X-Injected-Via-Gmane: http://gmane.org/
Original-Lines: 36
Original-X-Complaints-To: usenet@blaine.gmane.org
Cancel-Lock: sha1:39XbQdLTp3W3fy1cqPYipPnta5c=
X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic]
X-Received-From: 195.159.176.226
X-BeenThere: emacs-devel@gnu.org
X-Mailman-Version: 2.1.21
Precedence: list
List-Id: "Emacs development discussions." <emacs-devel.gnu.org>
List-Unsubscribe: <https://lists.gnu.org/mailman/options/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=unsubscribe>
List-Archive: <http://lists.gnu.org/archive/html/emacs-devel/>
List-Post: <mailto:emacs-devel@gnu.org>
List-Help: <mailto:emacs-devel-request@gnu.org?subject=help>
List-Subscribe: <https://lists.gnu.org/mailman/listinfo/emacs-devel>,
	<mailto:emacs-devel-request@gnu.org?subject=subscribe>
Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org
Original-Sender: "Emacs-devel" <emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org>
Xref: news.gmane.org gmane.emacs.devel:231143
Archived-At: <http://permalink.gmane.org/gmane.emacs.devel/231143>

>> Unfortunately some sites require to upload files in tar format and not
>> in tar.gz format.

Something like Dired's `Z` can't satisfy all imaginable cases, so the
fact some odd cases require the generation of uncompressed .tar file
shouldn't make much a difference in deciding what behavior we want.

> Yes.  Upload, download, email...  It's quite possible for
> a user to obtain a tar file, regardless of whether Stefan -

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".

> or even everyone here - considers tar.gz to be the only
> useful archive format.

Noone said tar.gz is the only useful format.  I just pointed out that in
my experience ".tar.gz" is itself considered as an archive format rather
than "a compressed file which contains an archive" 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.

> 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.


        Stefan