unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
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 19:02:12 +0300	[thread overview]
Message-ID: <838rr5mnej.fsf@gnu.org> (raw)
In-Reply-To: <871qwx2zv8.fsf@gnus.org> (message from Lars Ingebrigtsen on Fri,  13 May 2022 17:53:15 +0200)

> From: Lars Ingebrigtsen <larsi@gnus.org>
> Cc: pot@gnu.org,  25458@debbugs.gnu.org
> Date: Fri, 13 May 2022 17:53:15 +0200
> 
> Eli Zaretskii <eliz@gnu.org> writes:
> 
> > 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?
> 
> No, it would work just like when you read a tar.gz file -- we use
> external decompressors for that, too, even if we then parse the
> resulting tar file ourselves. 

Then I guess I don't understand what is the problem we are asked to
fix here.  Francesco, can you explain?





  reply	other threads:[~2022-05-13 16:02 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
2022-05-13 14:45     ` Francesco Potortì
2022-05-13 15:53     ` Lars Ingebrigtsen
2022-05-13 16:02       ` Eli Zaretskii [this message]
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=838rr5mnej.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).