eine

@pidgeon777, see #12: > The main point here is: do we want to design and maintain some new independent JSON schema to manage projects of (V)HDL sources? I think we...

At the moment there is no one explicitly working on "a JSON project file supported by GHDL". `hdl-prj.json` is just the most obvious conversion of GHDL's command-line options into a...

@pidgeon777, how are you installing GHDL, ghdl-ls and the Neovim client on WIndows?

To elaborate a bit further, ghdl-ls is tightly dependent on libghdl and the standard/ieee libs distributed as part of GHDL. Therefore, users cannot install any language server with any GHDL...

> How are you managing this compatibility issue right now in the language server? Currently, we are not managing it. `master` from this repo is expected to be compatible with...

> A simple solution is to move ghdl-ls into the ghdl repo. I think this is reasonable, given the small size of this project (the ls) and the tight dependency....

@danilofuchs, since this is experimental yet, you might want to have a look at rust_hdl. See jeremiah-c-leary/vhdl-style-guide#312 interesting.

- It seems that you moved the python server only. Are we going to keep this repo for the clients? - What about ghdl-ls/tests? If those are tests for the...

> All the python files are installed together; so I think we could get rid of libghdl-py. That makes sense. For now, libghdl-py is only used by the language server....

LSP Multi Server Example: https://github.com/Microsoft/vscode-extension-samples/tree/master/lsp-multi-server-sample > A language server example that demonstrates how to start a server per workspace folder. If the workspace has nested workspace folders only a server...