From: Marco Centurion <mcenturion@fing.edu.uy>
To: 10990@debbugs.gnu.org
Subject: bug#10990: 24.0.94; Uncompressing files
Date: Tue, 31 Aug 2021 13:20:01 -0300 [thread overview]
Message-ID: <87k0k18u32.fsf@fing.edu.uy> (raw)
In-Reply-To: <CAH8Pv0iRHeWmmxXicivmnff0p5uofvmh89C6WPFK7mH7nYhMAw@mail.gmail.com>
[-- Attachment #1: Type: text/plain, Size: 535 bytes --]
Given that we already use `gzip` in dired for other formats like `.tar.gz`
and `.tgz`, could we not just replace gunzip with `gzip -d`? I mean,
even in my (gnu/linux) system `gunzip` is just a script that passes
through to `gzip -d`.
I don't think that change would be a breaking one because we already
assume that `gzip` is present in the system and that `gzip -d`
decompresses files (again, the command for `.tar.gz` is "gzip -dc %i |
tar -xf -"). But if it is considered breaking, we could maybe add an
option to only use gzip?
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: bug#10990.patch --]
[-- Type: text/x-patch, Size: 761 bytes --]
diff --git a/lisp/dired-aux.el b/lisp/dired-aux.el
index 0b8c693b29..8e00af8f96 100644
--- a/lisp/dired-aux.el
+++ b/lisp/dired-aux.el
@@ -1137,12 +1137,12 @@ dired-compress-file-suffixes
("\\.tar\\.gz\\'" "" "gzip -dc %i | tar -xf -")
("\\.tar\\.xz\\'" "" "xz -dc %i | tar -xf -")
("\\.tgz\\'" "" "gzip -dc %i | tar -xf -")
- ("\\.gz\\'" "" "gunzip")
+ ("\\.gz\\'" "" "gzip -d")
("\\.lz\\'" "" "lzip -d")
("\\.Z\\'" "" "uncompress")
;; For .z, try gunzip. It might be an old gzip file,
;; or it might be from compact? pack? (which?) but gunzip handles both.
- ("\\.z\\'" "" "gunzip")
+ ("\\.z\\'" "" "gzip -d")
("\\.dz\\'" "" "dictunzip")
("\\.tbz\\'" ".tar" "bunzip2")
("\\.bz2\\'" "" "bunzip2")
[-- Attachment #3: Type: text/plain, Size: 90 bytes --]
--
Marco Centurion
Unidad de Recursos Informáticos
Facultad de Ingeniería - UdelaR
next prev parent reply other threads:[~2021-08-31 16:20 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 8:23 bug#10990: 24.0.94; Uncompressing files Dani Moncayo
2012-03-11 16:48 ` Eli Zaretskii
2012-03-11 21:50 ` Dani Moncayo
2012-03-12 3:52 ` Eli Zaretskii
2012-03-12 7:46 ` Dani Moncayo
2012-03-12 17:28 ` Juanma Barranquero
2012-03-12 17:29 ` Eli Zaretskii
2012-03-12 19:12 ` Dani Moncayo
2012-03-12 20:12 ` Stefan Monnier
2012-03-12 20:58 ` Eli Zaretskii
2012-03-12 17:58 ` Achim Gratz
2012-03-12 20:47 ` Achim Gratz
2012-03-12 20:59 ` Eli Zaretskii
2012-03-12 21:50 ` Achim Gratz
2021-08-31 16:20 ` Marco Centurion [this message]
2021-09-01 7:37 ` Lars Ingebrigtsen
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=87k0k18u32.fsf@fing.edu.uy \
--to=mcenturion@fing.edu.uy \
--cc=10990@debbugs.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).