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

Add support to go to definition in the whole workspace #182

Open
beyond-fu opened this issue Aug 27, 2023 · 2 comments
Open

Add support to go to definition in the whole workspace #182

beyond-fu opened this issue Aug 27, 2023 · 2 comments

Comments

@beyond-fu
Copy link

For now, veridian just supports to go to definition in the current file, but does not support to jump in the whole wordspace. https://github.com/imc-trading/svlangserver supports to go to definition/symbol in the whole workspace folder. So now I use veridian and svlangserver as my verilog/systemveilog LSP simultaneously. I hope veridian can support this feature.

Thanks!

@vivekmalneedi
Copy link
Owner

Sorry for the late reply, by default it should index all source files recursively from the working directory. If the working directory isn't where your files are then you'll need to have a veridian.yml configured to tell veridian where to look for your sources.
Also, if svlangserver is working for you, why would you need to run veridian as well, they should both be doing the same thing?

@beyond-fu
Copy link
Author

For now, veridian just supports to go to instance for the across files case according to my experience. It doesn't support to go to definition of the port of the instantiated module, go to the parameter definition(whether using define or package method) and some other features for the across files case.
For me, I use veridian to lint, format, do dot completion, and use svlangserver to hover, go to definition(also not support for parameters in other files).
Here is a short video about some features of svlangserver.

video.mp4

By the way, there is no perfect, fully-functional, easy-to-use LSP for v/sv for neovim for a long time. And I think the development of verible is too slow. That's frustrating:(

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

No branches or pull requests

2 participants