From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!.POSTED!not-for-mail From: Drew Adams Newsgroups: gmane.emacs.devel Subject: RE: [found the culprit] (was: [emacs -q versus empty .emacs file]) Date: Wed, 14 Nov 2018 09:10:19 -0800 (PST) Message-ID: <6cb2eae3-15ec-435e-8b7f-50213a7e52d9@default> References: <<<875zx1xgiq.fsf@mat.ucm.es>>> <<<83lg5w9956.fsf@gnu.org> <87d0r76ewm.fsf_-_@mat.ucm.es>>> <<<87tvkjq2mh.fsf_-_@mat.ucm.es>>> <<<834lcj8y1f.fsf@gnu.org>>> <> <<83y39v7gym.fsf@gnu.org>> NNTP-Posting-Host: blaine.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable X-Trace: blaine.gmane.org 1542215376 13722 195.159.176.226 (14 Nov 2018 17:09:36 GMT) X-Complaints-To: usenet@blaine.gmane.org NNTP-Posting-Date: Wed, 14 Nov 2018 17:09:36 +0000 (UTC) Cc: oub@mat.ucm.es, emacs-devel@gnu.org To: Eli Zaretskii , Drew Adams Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 14 18:09:31 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 1gMyfT-0003VN-3p for ged-emacs-devel@m.gmane.org; Wed, 14 Nov 2018 18:09:31 +0100 Original-Received: from localhost ([::1]:33444 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMyhZ-0007yV-HX for ged-emacs-devel@m.gmane.org; Wed, 14 Nov 2018 12:11:41 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:58330) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gMygT-0007Uk-TJ for emacs-devel@gnu.org; Wed, 14 Nov 2018 12:10:34 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gMygS-0006vE-WC for emacs-devel@gnu.org; Wed, 14 Nov 2018 12:10:33 -0500 Original-Received: from userp2130.oracle.com ([156.151.31.86]:56364) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.71) (envelope-from ) id 1gMygO-0006rR-OM; Wed, 14 Nov 2018 12:10:28 -0500 Original-Received: from pps.filterd (userp2130.oracle.com [127.0.0.1]) by userp2130.oracle.com (8.16.0.22/8.16.0.22) with SMTP id wAEH8qUi173946; Wed, 14 Nov 2018 17:10:27 GMT DKIM-Signature: v=1; a=rsa-sha256; c=relaxed/relaxed; d=oracle.com; h=mime-version : message-id : date : from : sender : to : cc : subject : references : in-reply-to : content-type : content-transfer-encoding; s=corp-2018-07-02; bh=ff5Df7DOY2v2DcXppYxhZ3KfP19c6Ha4LW0L4nJD1Wg=; b=wQSp+SoDOMWr9ct0E1e/BRvxlZKrhpA1A2qdUIGbRWHoPMMCNc5aKgB39OcOCaykHU8K kQhGAoYUV1WsVT+Q6zqd8ibOY1GEuMlU+PY0UUjC+6bDRIvZoWVAzM0+sqYBFkXlslP5 YDmu5duyozHRm82acvDi+EZKtjbFH1PaMGhaSmlQe8xWzdjoOv5WLZ6eTXLqER3Kuq9i ALaLCuB0fQIQYmA8mwep3tzK6HjSk9/pEMpP4nFftUvIdZT2yzvDVpl/c7uyaGfWiOty sDH3WFKSSB5PRoxibjA9beKjp1+xcaQZiQ+i6mrQ4ttJZ60RC61U+AgRPZ99tKZbsVhu QA== Original-Received: from aserv0022.oracle.com (aserv0022.oracle.com [141.146.126.234]) by userp2130.oracle.com with ESMTP id 2nr7cs4v3n-1 (version=TLSv1.2 cipher=ECDHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 14 Nov 2018 17:10:27 +0000 Original-Received: from userv0121.oracle.com (userv0121.oracle.com [156.151.31.72]) by aserv0022.oracle.com (8.14.4/8.14.4) with ESMTP id wAEHAKKn032408 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-GCM-SHA384 bits=256 verify=OK); Wed, 14 Nov 2018 17:10:21 GMT Original-Received: from abhmp0018.oracle.com (abhmp0018.oracle.com [141.146.116.24]) by userv0121.oracle.com (8.14.4/8.13.8) with ESMTP id wAEHAJIV010752; Wed, 14 Nov 2018 17:10:20 GMT In-Reply-To: <<83y39v7gym.fsf@gnu.org>> X-Priority: 3 X-Mailer: Oracle Beehive Extensions for Outlook 2.0.1.9.1 (1003210) [OL 16.0.4756.0 (x86)] X-Proofpoint-Virus-Version: vendor=nai engine=5900 definitions=9077 signatures=668683 X-Proofpoint-Spam-Details: rule=notspam policy=default score=0 suspectscore=0 malwarescore=0 phishscore=0 bulkscore=0 spamscore=0 mlxscore=0 mlxlogscore=792 adultscore=0 classifier=spam adjust=0 reason=mlx scancount=1 engine=8.0.1-1810050000 definitions=main-1811140154 X-detected-operating-system: by eggs.gnu.org: GNU/Linux 3.x [generic] X-Received-From: 156.151.31.86 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:231139 Archived-At: > > `Z' should be its own inverse. >=20 > It is. But there's a problem with "compressing" directories: Emacs > 26.1 introduced an ambiguity, because 'Z' on a directory produces a > .tar.gz archive out of its files, So a directory is a special case, if no one will have a tar file for a directory (so they only have tar.gz's). In that case a directory should be the same special case for inversing. We should not, I think change the general case for inversing compression just because in the case of a directory compression means something different. > but 'Z' on a .tar.gz file can either > uncompress to produce a .tar file or unpack all the files > into a directory. >=20 > > It's fine to have another key that unpacks a tar, or > > even another key that both uncompresses and unpacks. >=20 > Then someone will complain that 'Z' on a directory is not > its own inverse. See above. Either a directory is a special case or it's not. It sounds like it is. > > BTW, I don't see this change called out in NEWS for > > Emacs 26. Is it there and I just missed it? >=20 > It wasn't announced, and the manual wasn't updated to say what 'Z' > does in a directory. Shame on us. ;-) > > Compress or uncompress marked (or next prefix argument) files. > > A prefix argument ARG specifies files to use instead of marked. > > An integer means use the next ARG files (previous -ARG, if < 0). > > `C-u': Use the current file (whether or not any are marked). > > `C-u C-u': Use all files in Dired, except directories. > > `C-u C-u C-u': Use all files and directories, except `.' and `..'. > > `C-u C-u C-u C-u': Use all files and all directories. >=20 > Is "C-u 0' available? Depends on what you mean by available. `C-u 0' for `dired-do-*' commands means act on the next zero files. In the case of `Z' it (un)compresses no files. Should we leave it that way? I think so. You can invoke a `dired-do-*' command from Lisp code, and you might have code that expects zero to behave as it does now. I also think it's good for `dired-do-*' commands to share prefix-arg behavior, other things being equal. Should a zero numeric prefix arg be redefined for `dired-do-*' commands generally? I don't think so, but that could be something to consider. But back to square one: Is a directory special, in that no one will have a tar file for a directory - everyone will have only a tgz or a tar.gz file? If it is, then let `Z' special-case directories. Is that possible? To decompress a tar.gz it would try to decompress to a tar, but if the result is a directory then the result is, well, a directory and not a tar.