From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: [found the culprit] Date: Fri, 16 Nov 2018 09:48:24 +0200 Message-ID: <83efbl799z.fsf@gnu.org> References: <27024.1542249282@alto> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit X-Trace: blaine.gmane.org 1542354399 4042 195.159.176.226 (16 Nov 2018 07:46:39 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Fri, 16 Nov 2018 07:46:39 +0000 (UTC) Cc: emacs-devel@gnu.org To: =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 16 08:46:35 2018 Return-path: 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 ) id 1gNYpm-0000xb-9W for ged-emacs-devel@m.gmane.org; Fri, 16 Nov 2018 08:46:34 +0100 Original-Received: from localhost ([::1]:42540 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gNYrs-0001Xs-Pt for ged-emacs-devel@m.gmane.org; Fri, 16 Nov 2018 02:48:44 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:52519) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gNYrb-0001Tb-My for emacs-devel@gnu.org; Fri, 16 Nov 2018 02:48:28 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gNYrY-0004MQ-2R for emacs-devel@gnu.org; Fri, 16 Nov 2018 02:48:27 -0500 Original-Received: from fencepost.gnu.org ([2001:4830:134:3::e]:53091) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gNYrV-0004LQ-U6; Fri, 16 Nov 2018 02:48:23 -0500 Original-Received: from [176.228.60.248] (port=1907 helo=home-c4e4a596f7) by fencepost.gnu.org with esmtpsa (TLS1.2:RSA_AES_256_CBC_SHA1:256) (Exim 4.82) (envelope-from ) id 1gNYrV-0006b8-8Y; Fri, 16 Nov 2018 02:48:21 -0500 In-reply-to: (message from =?utf-8?Q?Cl=C3=A9ment?= Pit-Claudel on Thu, 15 Nov 2018 21:24:43 -0500) X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.2.x-3.x [generic] X-Received-From: 2001:4830:134:3::e X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.21 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: "Emacs-devel" Xref: news.gmane.org gmane.emacs.devel:231179 Archived-At: > From: Clément Pit-Claudel > Date: Thu, 15 Nov 2018 21:24:43 -0500 > > > The meaning of Z is to compress or uncompress. Extracting an archive is > > a different operation; it is semantically incoherent for Z to extract > > an archive. > > > > If we want a Dired command to extract archives, we should add one. > > It can handle .tgz files as well as .tar files and other archive types. > > I think this distinction (unpacking vs decompressing) is too subtle. What should we do on formats that support both, like zip? That is, should Z on a zip archive just change its compression mode to store, without extracting the files? Where there's only one meaning of Z, there's no problem. Hardly anyone would want Z on a zip archive to change the compression method; that's not what Z is about: it compresses or decompresses, and decompressing a zip archive _means_ unpacking it. But with .tar.gz files, decompressing and unpacking are two separate actions, so there's an ambiguity what Z might mean. And IMO (and also in Richard's, AFAIU), the ambiguity should be resolved in the least surprising way. Having all the files from an archive extracted without my explicit permission is a surprise, might even be unpleasant surprise.