From: Jim Porter <jporterbugs@gmail.com>
To: Philip Kaludercic <philipk@posteo.net>
Cc: 64985@debbugs.gnu.org
Subject: bug#64985: 29.1; [PATCH] Byte-compilation of packages via package-vc doesn't correctly handle .elpaignore wildcards
Date: Tue, 1 Aug 2023 09:10:38 -0700 [thread overview]
Message-ID: <fbec1483-c2b2-f394-5366-e023281b5da8@gmail.com> (raw)
In-Reply-To: <87edknj6nf.fsf@posteo.net>
On 8/1/2023 5:20 AM, Philip Kaludercic wrote:
> Jim Porter <jporterbugs@gmail.com> writes:
>
>> When using the various package-vc installation functions, Emacs
>> byte-compiles the source (good). However, it doesn't ignore sources
>> that match wildcards in ".elpaignore" (bad). That's because, even
>> though 'byte-compile-ignore-files' is documented to be a list of
>> regexps, 'byte-recompile-directory' treats it as a list of strings.
>
> I am a bit confused about this point. Why do you think that
> `byte-recompile-directory' treads `byte-compile-ignore-files' as a list
> of non-regexp strings?
The docstring for 'regexp-opt' (which is what 'byte-recompile-directory'
uses to combine 'byte-compile-ignore-files') says this:
Return a regexp to match a string in the list STRINGS.
Each member of STRINGS is treated as a fixed string, not as a regexp.
> Here also, instead of merging a list of regular expressions into a
> disjunctive one, you match each individually. Am I missing something,
> or what does this change?
>
> (string-match-p (regexp-opt '("foo" "bar" "baz")) "foo") ;=> 0
> (seq-some (lambda (ex) (string-match-p ex "foo")) '("foo" "bar" "baz")) ;=> 0
Consider this case:
(string-match-p (regexp-opt '("fo+" "bar")) "foo") ;=> nil
(seq-some (lambda (ex) (string-match-p ex "foo")) '("fo+" "bar")) ;=> 0
There might be another way to do this, e.g. so that we could optimize
the regexp, but I'm not sure if Emacs has anything to optimize a list of
*regexp* alternatives (rather than a list of *string* alternatives). I
tested out 'rx' too, but no luck there either. This seemed like the best
I could do without more extensive changes, which I wanted to avoid for
the 29 branch.
next prev parent reply other threads:[~2023-08-01 16:10 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-01 6:20 bug#64985: 29.1; [PATCH] Byte-compilation of packages via package-vc doesn't correctly handle .elpaignore wildcards Jim Porter
2023-08-01 11:21 ` Eli Zaretskii
2023-08-01 19:22 ` Jim Porter
2023-08-01 12:20 ` Philip Kaludercic
2023-08-01 16:10 ` Jim Porter [this message]
2023-08-01 16:18 ` Jim Porter
2023-08-01 17:29 ` Mattias Engdegård
2023-08-01 18:10 ` Jim Porter
2023-08-01 18:32 ` Philip Kaludercic
2023-08-01 19:18 ` Jim Porter
2023-08-01 19:21 ` Philip Kaludercic
2023-08-02 18:08 ` Jim Porter
2023-08-04 19:37 ` bug#64985: 30.0.50; package-recompile-all and package-recompile do not recompile anything, seems related to the patch associated with bug #64985 Vincenzo Pupillo
2023-08-04 20:05 ` Jim Porter
2023-08-05 17:12 ` Mattias Engdegård
2023-08-05 17:16 ` Jim Porter
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=fbec1483-c2b2-f394-5366-e023281b5da8@gmail.com \
--to=jporterbugs@gmail.com \
--cc=64985@debbugs.gnu.org \
--cc=philipk@posteo.net \
/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).