From: Eli Zaretskii <eliz@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25458@debbugs.gnu.org, pot@gnu.org
Subject: bug#25458: 25.1; tar mode does not handle compressed archives without specific extensions
Date: Fri, 13 May 2022 17:18:56 +0300 [thread overview]
Message-ID: <83ilq9ms6n.fsf@gnu.org> (raw)
In-Reply-To: <87o801serb.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri, 13 May 2022 16:12:24 +0200)
> Cc: 25458@debbugs.gnu.org
> From: Lars Ingebrigtsen <larsi@gnus.org>
> Date: Fri, 13 May 2022 16:12:24 +0200
>
> Francesco Potortì <pot@gnu.org> writes:
>
> > By looking at the comments on top of tar-mode.el, I get that it does not
> > rely on tar to get the archive listing, but reads the archive itself, so
> > correcting this problem does not appear straightforward to me...
>
> (I'm going through old bug reports that unfortunately weren't resolved
> at the time.)
>
> If Emacs had code to automatically recognise compressed data, I guess
> tar-mode could decompress the buffer before it started working on it.
> (Does Emacs have that? I guess we could add stuff to
> `magic-fallback-mode-alist' or something in that region...)
But decompressing means, for most compression types, running an
external program on the file. Or does OP suggest that we link Emacs
against libbz2, liblz4, liblzma, etc. to have these decompression
methods available in core?
next prev parent reply other threads:[~2022-05-13 14:18 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-16 15:20 bug#25458: 25.1; tar mode does not handle compressed archives without specific extensions Francesco Potortì
2022-05-13 14:12 ` Lars Ingebrigtsen
2022-05-13 14:18 ` Eli Zaretskii [this message]
2022-05-13 14:45 ` Francesco Potortì
2022-05-13 15:53 ` Lars Ingebrigtsen
2022-05-13 16:02 ` Eli Zaretskii
2022-05-13 22:25 ` Francesco Potortì
2022-05-14 6:15 ` Eli Zaretskii
2022-05-13 14:36 ` Francesco Potortì
2022-05-13 15:54 ` Lars Ingebrigtsen
2022-05-13 22:18 ` Francesco Potortì
2022-05-14 1:13 ` Lars Ingebrigtsen
2022-05-16 14:24 ` Francesco Potortì
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=83ilq9ms6n.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=25458@debbugs.gnu.org \
--cc=larsi@gnus.org \
--cc=pot@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).