From: Oleh Krehel <ohwoeowho@gmail.com>
To: Eli Zaretskii <eliz@gnu.org>
Cc: emacs-devel@gnu.org
Subject: Re: master 6d6bf46 2/2: Make dired-do-compress work for *.tar.gz files
Date: Fri, 16 Oct 2015 15:47:03 +0200 [thread overview]
Message-ID: <87wpunsz6w.fsf@gmail.com> (raw)
In-Reply-To: <83si5b54m9.fsf@gnu.org> (Eli Zaretskii's message of "Fri, 16 Oct 2015 16:23:42 +0300")
Eli Zaretskii <eliz@gnu.org> writes:
>> OK, is this what you want for compression:
>>
>> tar -c example/ | gzip -c9 > example.tar.gz
>
> Yes.
OK, I propose the following entry in `dired-compress-file-suffixes' to
be used when "Z" is pressed on a directory:
(t ".tar.gz" "tar -c %i | gzip -c9 > %o")
>> And this for decompression:
>>
>> gzip -dc example.tar.gz | tar -x
>
> Yes (except that you could use gunzip.)
So:
gunzip -dc example.tar.gz | tar -x
and the corresponding entry in `dired-compress-file-suffixes':
("\\.tar\\.gz\\'" "" "gunzip -dc %i | tar -xv")
Also, what is the difference between gzip and gunzip? Both seem to work
the same in this case.
>> I think it would be productive if everyone just wrote down the explicit
>> shell command they want with all the relevant switches.
>
> I don't understand: who are those "everyone" that you want to write
> the commands?
Well, Paul has a weird tar that doesn't understand "-z", so I wonder
what exact command he uses for *.tar.gz.
next prev parent reply other threads:[~2015-10-16 13:47 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20151013135354.28594.43074@vcs.savannah.gnu.org>
[not found] ` <E1Zm01b-0007SW-BB@vcs.savannah.gnu.org>
2015-10-13 18:28 ` master 6d6bf46 2/2: Make dired-do-compress work for *.tar.gz files Glenn Morris
2015-10-13 18:38 ` Paul Eggert
2015-10-14 7:58 ` Oleh Krehel
2015-10-14 15:17 ` Paul Eggert
2015-10-14 7:56 ` Oleh Krehel
2015-10-14 16:16 ` Eli Zaretskii
2015-10-14 18:51 ` Achim Gratz
2015-10-14 19:02 ` Eli Zaretskii
2015-10-15 13:07 ` Oleh Krehel
2015-10-15 15:55 ` Eli Zaretskii
2015-10-15 19:46 ` Achim Gratz
2015-10-15 16:48 ` Glenn Morris
2015-10-15 17:06 ` Eli Zaretskii
2015-10-16 10:44 ` Oleh Krehel
2015-10-16 13:23 ` Eli Zaretskii
2015-10-16 13:47 ` Oleh Krehel [this message]
2015-10-16 14:35 ` Eli Zaretskii
2015-10-20 8:59 ` Oleh Krehel
2015-10-20 14:57 ` Eli Zaretskii
2015-10-21 7:57 ` Oleh Krehel
2015-10-21 15:04 ` Oleh Krehel
2015-10-21 16:28 ` Eli Zaretskii
2015-10-22 10:59 ` Oleh Krehel
2015-10-20 22:51 ` Juri Linkov
2015-10-21 8:00 ` Oleh Krehel
2015-10-16 15:35 ` Paul Eggert
2015-10-16 16:11 ` Eli Zaretskii
2015-10-16 16:26 ` Glenn Morris
2015-10-16 12:11 ` Oleh Krehel
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=87wpunsz6w.fsf@gmail.com \
--to=ohwoeowho@gmail.com \
--cc=eliz@gnu.org \
--cc=emacs-devel@gnu.org \
/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).