all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: "Francesco Potortì" <pot@gnu.org>
To: Lars Ingebrigtsen <larsi@gnus.org>
Cc: 25458@debbugs.gnu.org
Subject: bug#25458: 25.1; tar mode does not handle compressed archives without specific extensions
Date: Fri, 13 May 2022 16:36:20 +0200	[thread overview]
Message-ID: <87v8u9mrdn.fsf@tucano.isti.cnr.it> (raw)
In-Reply-To: <87o801serb.fsf@gnus.org> (larsi@gnus.org)

I am not saying that it's worth the trouble, and anyway I would not have the time to help working on it, sorry.  However, here is some food for thought.

>> 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 I think the question is -- do we want to support this?  I'm not
>quite sure -- it would be pretty unusual for a mode to do something like
>this, and it's not clear what the semantics should be.  That is, if
>we're saving the tar buffer afterwards, should it be compressed or not?
>Either option would surprise somebody.

Not really.  If I read a compressed file, Emacs uncompresses it when loading it to a buffer, then you can edit it and save it.  Compression and decompression are transparent.  I use this feature quite often, and so I am led to expect it of compressed archives too.  If it was compressed to begin with, it should be saved compressed too.

>And finally -- is this a thing that actually exists in the wild?  I
>don't think I've ever seen a compressed tar file that didn't have a name
>that indicated how it was compressed.

Hm, maybe it's only me, but I routinely produce tar files without any compression suffix, as tar automatically does the right thing with compressed archives (it has done for many years now).  I think that adding compression suffixes to tar files is (should be?) a thing of the past.

>So due to both the unclear semantics and that I doubt the utility, I'm
>inclined to close this as a "wontfix".  Anybody got any opinions?

I definitely think that it would be useful, and the semantics is clear at least to me (I may miss things, obviously).  However, that needs someone implementing it who thinks the same...

-- fp





  parent reply	other threads:[~2022-05-13 14:36 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ì
2022-05-14  6:15           ` Eli Zaretskii
2022-05-13 14:36   ` Francesco Potortì [this message]
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=87v8u9mrdn.fsf@tucano.isti.cnr.it \
    --to=pot@gnu.org \
    --cc=25458@debbugs.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.