From: "Francesco Potortì" <pot@gnu.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: 25458@debbugs.gnu.org, Lars Ingebrigtsen <larsi@gnus.org>
Subject: bug#25458: 25.1; tar mode does not handle compressed archives without specific extensions
Date: Sat, 14 May 2022 00:25:36 +0200 [thread overview]
Message-ID: <87r14xm5nj.fsf@tucano.isti.cnr.it> (raw)
In-Reply-To: <838rr5mnej.fsf@gnu.org> (eliz@gnu.org)
>> 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?
If I read foo.tar into Emacs, where foo.tar was created with
$ tar -Jcf foo.tar any.file.name
then Emacs does not recognise it as a tar file. Instead, it should look at it, understand that it is a compressed tar file, uncompress and parse it. If asked to save it after modification, it should compress it before saving, using the same compression method that was used in the first place.
Compression would be transparent to Emacs if it relied on Tar for parsing the tar file, because Tar manages compressed files transparently. But since Emacs parses the tar file itself, it should behave as Tar does, that is, uncompress the file if it was compressed in the first place, and recompress when saving it after editing.
next prev parent reply other threads:[~2022-05-13 22:25 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
2022-05-13 22:25 ` Francesco Potortì [this message]
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87r14xm5nj.fsf@tucano.isti.cnr.it \
--to=pot@gnu.org \
--cc=25458@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.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.