Silence "Function provided is already compiled"#83
Open
jessiehildebrandt wants to merge 1 commit into
Open
Conversation
alphapapa
force-pushed
the
master
branch
3 times, most recently
from
9333643 to
84e837f
Compare
|
Why was this never merged? Every time Emacs starts up, I get |
Owner
Probably for the same reason that anything on any of your own to-do lists hasn't gotten done yet. Anyway, looking at this patch, I'm not sure that it's the best solution. As well, I don't get that error when I start Emacs, so there might be an issue with your installation or configuration. |
alphapapa
added
bug
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
It looks like some native-comp Emacs 28 configurations pre-compile the anonymous byte-compiled functions in
bufler.elandbufler-group-tree.el, causing the editor to fuss in the echo area when invoking certain bufler commands.I see a similar issue (#28) was reported before, but that it was closed pending some fundamental changes in v0.4. While those changes are being worked on, this patch should presently remediate the issue.