all messages for Emacs-related lists mirrored at yhetil.org
 help / color / mirror / code / Atom feed
From: Lars Ingebrigtsen <larsi@gnus.org>
To: Eli Zaretskii <eliz@gnu.org>
Cc: trentbuck@gmail.com, Michael Albinus <michael.albinus@gmx.de>,
	52477@debbugs.gnu.org, stefan@marxist.se
Subject: bug#52477: 27.1; .crx and .crx3 are zip files
Date: Sun, 19 Dec 2021 14:09:10 +0100	[thread overview]
Message-ID: <87y24grbbd.fsf@gnus.org> (raw)
In-Reply-To: <83fsqshehh.fsf@gnu.org> (Eli Zaretskii's message of "Thu, 16 Dec 2021 15:21:46 +0200")

Eli Zaretskii <eliz@gnu.org> writes:

> Me neither, but if someone wants to extend arc-mode.el to support
> those extension, that would be welcome, I think.  My point is that we
> cannot just add this file type before we implement those extensions.

Yup.  arc-mode hard-code a lot of knowledge about zip files, including
the "PK" header and stuff.  It's possible that that can just be replaced
with Cr24, but it seems rather unlikely that Google would create a new
zip file format if that was the only difference, I'd have thought?

(But I have no knowledge here.)

-- 
(domestic pets only, the antidote for overdose, milk.)
   bloggy blog: http://lars.ingebrigtsen.no





  reply	other threads:[~2021-12-19 13:09 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-12-14  4:56 bug#52477: 27.1; .crx and .crx3 are zip files Trent W. Buck
2021-12-15 20:51 ` Stefan Kangas
2021-12-16  8:56   ` Michael Albinus
2021-12-16  9:22     ` Eli Zaretskii
2021-12-16 11:59       ` Michael Albinus
2021-12-16 13:21         ` Eli Zaretskii
2021-12-19 13:09           ` Lars Ingebrigtsen [this message]
2021-12-22  3:50           ` Trent W. Buck
2021-12-22 12:20             ` Michael Albinus
2021-12-23  4:01               ` Trent W. Buck
2021-12-24 13:51                 ` Michael Albinus
2021-12-22 12:55             ` Eli Zaretskii

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=87y24grbbd.fsf@gnus.org \
    --to=larsi@gnus.org \
    --cc=52477@debbugs.gnu.org \
    --cc=eliz@gnu.org \
    --cc=michael.albinus@gmx.de \
    --cc=stefan@marxist.se \
    --cc=trentbuck@gmail.com \
    /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.