From: Devon Sean McCullough <Emacs-Hacker2017@jovi.net>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: 29235@debbugs.gnu.org
Subject: bug#29235: 26.0.50; tar.xz broken
Date: Fri, 10 Nov 2017 09:24:01 -0500 [thread overview]
Message-ID: <F43218D0-200B-4417-AA34-5DDE9FFE7785@jovi.net> (raw)
In-Reply-To: <87375m1nkk.fsf@linux-m68k.org>
> On Nov 10, 2017, at 4:37 AM, Andreas Schwab <schwab@linux-m68k.org> wrote:
>
> On Nov 09 2017, Devon Sean McCullough <Emacs-Hacker2017@jovi.net> wrote:
>
>> Note that MacOSX lacks xz
>
> Not even under a different name?
Turns out xz is redundant because gunzip, gzcat and zcat all work.
Peace
—Devon
P.S. Transcript follows:
$ for C in cat gzcat zcat gunzip; do echo -en "$C\t"; "$C" < bar.tar.xz | hexdump -C | head -1; done
cat 00000000 fd 37 7a 58 5a 00 00 04 e6 d6 b4 46 02 00 21 01 |.7zXZ......F..!.|
gzcat 00000000 62 61 72 00 00 00 00 00 00 00 00 00 00 00 00 00 |bar.............|
zcat 00000000 62 61 72 00 00 00 00 00 00 00 00 00 00 00 00 00 |bar.............|
gunzip 00000000 62 61 72 00 00 00 00 00 00 00 00 00 00 00 00 00 |bar.............|
P.P.S. Users need to list and retrieve archived files.
MacOSX bsdtar -tv and -xO provide these capabilities.
I’ve never heard of anyone saving archives from Emacs
so dired and find-file satisfy 99% of mundane user needs.
Other requirements are artifacts of a brittle implementation
which, fortunately in this particular case, is sufficient after all.
next prev parent reply other threads:[~2017-11-10 14:24 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-09 21:41 bug#29235: 26.0.50; tar.xz broken Devon Sean McCullough
2017-11-10 7:47 ` Eli Zaretskii
2017-11-10 9:37 ` Andreas Schwab
2017-11-10 14:24 ` Devon Sean McCullough [this message]
2021-09-03 7:10 ` bug#29235: Builtin bsdtar decompression for .tar.xz not used Lars Ingebrigtsen
2021-09-03 10:24 ` Andreas Schwab
2021-09-03 10:45 ` Lars Ingebrigtsen
2021-09-24 15:07 ` Robert Pluim
2021-09-25 1:06 ` 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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=F43218D0-200B-4417-AA34-5DDE9FFE7785@jovi.net \
--to=emacs-hacker2017@jovi.net \
--cc=29235@debbugs.gnu.org \
--cc=schwab@linux-m68k.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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.