Update variable name for source to avoid function name conflict #1105
Conversation
This file contains 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
``` Error detected while processing function clap#[45]..clap#open_provider[23]..<SNR>45_detect_source_type: line 1: E705: Variable name conflicts with existing function: Source ```
|
Look good to me. CI failure is unrelated. |
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.
Hi @liuchengxu,
I am adding PR to update variable name from
SourcetoClapProviderSourceto avoid function name conflict. In my case, I have aSourcefunction to source vim config. I can change my config to fix this issue but I think thatSourceis quite common function name, others can be affected by this error as well. Please help me to review and accept this PR if you find it does make senses, thanks.