unofficial mirror of emacs-devel@gnu.org 
 help / color / mirror / code / Atom feed
From: Drew Adams <drew.adams@oracle.com>
To: Eli Zaretskii <eliz@gnu.org>, Drew Adams <drew.adams@oracle.com>
Cc: oub@mat.ucm.es, emacs-devel@gnu.org
Subject: RE: [found the culprit] (was: [emacs -q versus empty .emacs file])
Date: Wed, 14 Nov 2018 09:10:19 -0800 (PST)	[thread overview]
Message-ID: <6cb2eae3-15ec-435e-8b7f-50213a7e52d9@default> (raw)
In-Reply-To: <<83y39v7gym.fsf@gnu.org>>

> > `Z' should be its own inverse.
> 
> 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.
> 
> > It's fine to have another key that unpacks a tar, or
> > even another key that both uncompresses and unpacks.
> 
> 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?
> 
> 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.
> 
> 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.



      parent reply	other threads:[~2018-11-14 17:10 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
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             ` Drew Adams [this message]
     [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=6cb2eae3-15ec-435e-8b7f-50213a7e52d9@default \
    --to=drew.adams@oracle.com \
    --cc=eliz@gnu.org \
    --cc=emacs-devel@gnu.org \
    --cc=oub@mat.ucm.es \
    /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).