Skip to content
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

Define project path to find all code dependencies #37

Open
a1gituser opened this issue Mar 12, 2024 · 3 comments
Open

Define project path to find all code dependencies #37

a1gituser opened this issue Mar 12, 2024 · 3 comments
Labels
enhancement New feature or request

Comments

@a1gituser
Copy link

I'm currently able to setup and use matlab_ls under neovim. However, one of the projects I work on has multiple functions and scripts defined in different folder paths. Usually these are added with some setup scripts so as to not contaminate the path with unnecessary entries when working with other projects.

Is it possible to setup the LSP to load these paths via a script or some other setting? Is there a different approach to help the language server find my function definitions?

thanks!

@a1gituser a1gituser added the bug Something isn't working label Mar 12, 2024
@dklilley
Copy link
Member

Thanks for raising this!

This seems similar to mathworks/MATLAB-extension-for-vscode#98. Do you think these are the same, or do you have additional requirements to address your pain?

@dklilley dklilley added enhancement New feature or request and removed bug Something isn't working labels Mar 12, 2024
@J-Sorenson
Copy link

This seems similar to mathworks/MATLAB-extension-for-vscode#98. Do you think these are the same, or do you have additional requirements to address your pain?

I suppose it could be implemented in the VSCode extension by way of a startup script (if the language server supports that). It may be cleaner to implement path definitions in the language server, though. It would be nice to specify paths in the project workspace preferences in a generic fashion in order to support multiple editors.

@a1gituser
Copy link
Author

Yes they're similar, and agree that having the option to execute a script like startup.m would take care of this. Whether it is fixed (i.e., always startup.m) or defined in options per project would be awesome. And I think it would fix my issue.

Thanks for showing me the other issue! That was helpful.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

3 participants