unofficial mirror of help-gnu-emacs@gnu.org
 help / color / mirror / Atom feed
From: Robert Pluim <rpluim@gmail.com>
To: help-gnu-emacs@gnu.org
Subject: Re: Error opening an APK file
Date: Fri, 20 Sep 2019 14:23:39 +0200	[thread overview]
Message-ID: <m2lfujyx4k.fsf@gmail.com> (raw)
In-Reply-To: jwvef0bgo6p.fsf-monnier+emacs@gnu.org

>>>>> On Fri, 20 Sep 2019 08:14:37 -0400, Stefan Monnier <monnier@iro.umontreal.ca> said:

    Stefan> Eli Zaretskii [2019-09-20 10:26:31] wrote:
    >>> From: Pascal Quesseveur <pquessev@gmail.com>
    >>> Date: Thu, 19 Sep 2019 09:15:00 +0200
    >>> 
    >>> >"EZ" == Eli Zaretskii <eliz@gnu.org> writes:
    >>> 
    EZ> Are you saying that just renaming a .apk file to .zip solves the
    EZ> problem?
    >>> 
    >>> Yes. In files.el auto-mode-alist associates archive-mode for archive
    >>> file extensions: arc, zip, ...  The comment says:
    >>> 
    >>> ;; The list of archive file extensions should be in sync with
    >>> ;; `auto-coding-alist' with `no-conversion' coding system.
    >>> 
    >>> In fact, auto-coding-alist in mule.el associates archive file
    >>> extensions with no-conversion-multibyte.
    >> 
    >> And if you add apk to auto-coding-alist, the problem goes away?

    Stefan> How 'bout a patch along the lines of the one below?


    Stefan>         Stefan


    Stefan> diff --git a/lisp/international/mule.el b/lisp/international/mule.el
    Stefan> index ec6f647688..c570caa993 100644
    Stefan> --- a/lisp/international/mule.el
    Stefan> +++ b/lisp/international/mule.el
    Stefan> @@ -1844,12 +1843,9 @@ auto-coding-alist
    Stefan>    ;; .exe and .EXE are added to support archive-mode looking at DOS
    Stefan>    ;; self-extracting exe archives.
    Stefan>    (mapcar (lambda (arg) (cons (purecopy (car arg)) (cdr arg)))
    Stefan> -	  '(("\\.\\(\
    Stefan> -arc\\|zip\\|lzh\\|lha\\|zoo\\|[jew]ar\\|xpi\\|rar\\|7z\\|\
    Stefan> -ARC\\|ZIP\\|LZH\\|LHA\\|ZOO\\|[JEW]AR\\|XPI\\|RAR\\|7Z\\)\\'"

Why upcase the extensions? My .zip files are named .zip, and I have a
case-sensitive file system.

Robert




  reply	other threads:[~2019-09-20 12:23 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-09-18  8:52 Error opening an APK file Pascal Quesseveur
2019-09-18 12:35 ` Eli Zaretskii
2019-09-18 14:20   ` Pascal Quesseveur
2019-09-18 14:29     ` Eli Zaretskii
2019-09-18 15:11       ` Pascal Quesseveur
2019-09-18 15:27         ` Eli Zaretskii
2019-09-18 16:48           ` Pascal Quesseveur
2019-09-19  7:15           ` Pascal Quesseveur
2019-09-20  7:26             ` Eli Zaretskii
2019-09-20 12:14               ` Stefan Monnier
2019-09-20 12:23                 ` Robert Pluim [this message]
2019-09-20 12:40                   ` Stefan Monnier
2019-09-20 12:47                     ` Robert Pluim
2019-09-20 14:35                     ` Eli Zaretskii
2019-09-20 15:13                       ` Stefan Monnier
2019-09-20 16:02                         ` Eli Zaretskii
2019-09-20 13:01                   ` Eli Zaretskii
2019-09-20 13:17                     ` Robert Pluim
2019-09-20 14:37                 ` 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

  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=m2lfujyx4k.fsf@gmail.com \
    --to=rpluim@gmail.com \
    --cc=help-gnu-emacs@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.
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).