From: Stefan Monnier <monnier@IRO.UMontreal.CA>
To: emacs-devel@gnu.org
Cc: Michael Heerdegen <michael_heerdegen@web.de>
Subject: Re: [elpa] master 1093871 1/4: Fix disregarding compressed elisp files
Date: Tue, 20 Dec 2016 09:54:51 -0500 [thread overview]
Message-ID: <jwvvauebqhj.fsf-monnier+emacsdiffs@gnu.org> (raw)
In-Reply-To: <20161220065102.4ED75220145@vcs.savannah.gnu.org> (Michael Heerdegen's message of "Tue, 20 Dec 2016 06:51:02 +0000 (UTC)")
> - (and (string-match-p "\\.el\\'" file)
> + (and (string-match-p "\\.el\\(\\.\\(gz\\|Z\\)\\)?\\'" file)
Why not use jka-compr-load-suffixes?
Stefan
next parent reply other threads:[~2016-12-20 14:54 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20161220065102.21832.2048@vcs.savannah.gnu.org>
[not found] ` <20161220065102.4ED75220145@vcs.savannah.gnu.org>
2016-12-20 14:54 ` Stefan Monnier [this message]
2016-12-22 17:28 ` [elpa] master 1093871 1/4: Fix disregarding compressed elisp files Michael Heerdegen
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=jwvvauebqhj.fsf-monnier+emacsdiffs@gnu.org \
--to=monnier@iro.umontreal.ca \
--cc=emacs-devel@gnu.org \
--cc=michael_heerdegen@web.de \
/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).