Skip to content

fix(cli): some package files not being byte-compiled (2nd take) #8247

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 1 commit into from
Feb 21, 2025

Conversation

real-or-random
Copy link
Contributor

@real-or-random real-or-random commented Jan 17, 2025

This reverts a workaround for straight that is no longer necessary because it has been applied upstream and we've bumped the package since.

For some reason I don't understand, this reproducibly fixes a reoccurrence of the original problem for me: Before this commit, some files of the citar package were not byte-compiled. After this commit,the problem is gone.

This effectively reverts 54a084f, though it's not a reverting commit in strict sense because the code has been moved to a different file.

Revert: 54a084f
Ref: d80c5e5
Ref: #7707
Ref: radian-software/straight.el#1132
Ref: https://discourse.doomemacs.org/t/is-it-expected-that-doom-sync-does-not-byte-compile-native-compile-some-files/4946


  • I searched the issue tracker and this hasn't been PRed before.
  • My changes are not on the do-not-PR list for this project.
  • My commits conform to Doom's git conventions.
  • My changes are visual; I've included before and after screenshots.
  • I am blindly checking these off.
  • Any relevant issues or PRs have been linked to.
  • This a draft PR; I need more time to finish it.

@real-or-random real-or-random requested a review from a team as a code owner January 17, 2025 00:41
This reverts a workaround for straight that is no longer necessary
because it has been applied upstream and we've bumped the package since.

For some reason I don't understand, this reproducibly fixes a
reoccurrence of the original problem for me: Before this commit, some
files of the citar package were not byte-compiled. After this commit,
the problem is gone.

This effectively reverts 54a084f, though it's not a reverting
commit in strict sense because the code has been moved to a different
file.

Revert: 54a084f
Ref: d80c5e5
Ref: doomemacs#7707
Ref: radian-software/straight.el#1132
Ref: https://discourse.doomemacs.org/t/is-it-expected-that-doom-sync-does-not-byte-compile-native-compile-some-files/4946
@hlissner hlissner added is:bug Something isn't working as intended module:core:cli Pertains to the `$ doom` script re:straight To do with straight; our package manager labels Jan 17, 2025
@hlissner hlissner added this to the core v3.0 milestone Jan 17, 2025
@real-or-random real-or-random force-pushed the 202501-byte-compile-cli branch from ad690c1 to 22f1d20 Compare January 17, 2025 00:45
@real-or-random
Copy link
Contributor Author

Sorry, force-pushed just to improve the commit message. Ready now.

@hlissner hlissner merged commit 2bceb21 into doomemacs:master Feb 21, 2025
@hlissner
Copy link
Member

LGTM! Thanks again for your help!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
is:bug Something isn't working as intended module:core:cli Pertains to the `$ doom` script re:straight To do with straight; our package manager
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants