fix cpath related errors#166
Merged
Merged
Conversation
ff118e3 to
0b95ecb
Compare
Contributor
Author
|
ah, right, I didn't see that PR, thanks |
Owner
|
I'll keep the other PR, thank you both for contributing. And sorry for the delay |
Owner
|
No I actually will keep this one because I can not update that PR cause github sucks |
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
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.
Current way of configuring cpath use the full path of the downloaded binary without any '?', this causes any require statement that can't resolve before this cpath component to always resolve to the downloaded libfff_nvim, thus causing some unexpected bug in some other plugins or user code.
fixes errors like this: