We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
source
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
Neovim
Linux & OS X
4.9.0
This is a very rough example
Create the following file:
#!/bin/sh # lib.sh hello() { echo "Hello, world!" }
Source the file via string concatenation:
#!/bin/sh # main.sh PROJECT_DIR="/Users/David.Ross/temp" source "${PROJECT_DIR}/libs/lib.sh" hello
Hover over hello and execute go to definition. This will not work.
hello
Edit the main.sh to the following:
main.sh
#!/bin/sh # main.sh PROJECT_DIR="/Users/David.Ross/temp" source /Users/David.Ross/temp/libs/lib.sh hello
Hover over hello and execute go to definition, this will now work.
Is go-to-definition not intended to work when part of the path is part of a variable?
No response
It should go to definition even when sourcing a path by string concatenation (var + substring).
The text was updated successfully, but these errors were encountered:
No branches or pull requests
Code editor
Neovim
Platform
Linux & OS X
Version
4.9.0
What steps will reproduce the bug?
This is a very rough example
Create the following file:
Source the file via string concatenation:
Hover over
hello
and execute go to definition. This will not work.Edit the
main.sh
to the following:Hover over
hello
and execute go to definition, this will now work.Is go-to-definition not intended to work when part of the path is part of a variable?
How often does it reproduce? Is there a required condition?
No response
What is the expected behavior?
No response
What do you see instead?
It should go to definition even when sourcing a path by string concatenation (var + substring).
Additional information
No response
The text was updated successfully, but these errors were encountered: