fix inclusion of bytecomp variables

[Stebalien]

The regexp was inclusing all variables ending with byte, not variables starting with byte-.

[thierryvolpiatto]

Basil L. Contovounesios notifications@github.com writes:

@basil-conto commented on this pull request.

━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━

In async-bytecomp.el:

@@ -91,7 +91,7 @@ All *.elc files are systematically deleted before proceeding." (async-start `(lambda () (require 'bytecomp)

• ,(async-inject-variables "\`\(load-path\)\|byte\'")
• ,(async-inject-variables "\`\(load-path\'\|byte-\)")

By shy I mean \(?:...\) instead of \(...\), as I don't see the captured match group being used anywhere, though I could be wrong.

You are right the match group is not used, you can use the shy group safely.

-- Thierry

[thierryvolpiatto]

Thanks merged!