-
Notifications
You must be signed in to change notification settings - Fork 63
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 a switch to load configuration from a file. #1108
Comments
Hello! That's a very interesting idea indeed. Do you know other language servers that provide this option? |
Hi,
Thanks.
None I'm aware of. |
Ok! In any case, looks like a good idea, we'll add the option. |
That's good news 😃 |
Just remembered that language servers for VHDL use a configuration file to manage specific configuration parameters (like libraries content, top level entity...). For example : |
Add --config option to specify a server configuration Closes #1108 See merge request eng/ide/ada_language_server!1135
👍 |
Can you provide a
|
the same for me |
Hello @NicoPy , Do you have a config that exhibits the issue? I have tested with a simple config file that just sets the |
Actually the issue only exists with the ada_language_server packaged with the extension. We are able to reproduce now. Thanks for reporting! |
when Self.Root hasn't been set yet by Initialize request, but Change_Configuration relies on it. Refs #1108
As mentioned in another issue, I'm trying to use ALS with Eclipse (without writing a dedicated Eclipse plugin).
The Eclipse 'language server' client has, of course, no knowledge of ALS additional configuration parameters.
What would be very useful is to be able to add a
config
(or similar) switch to ALS to provide a file path containing ALS configuration.One could then use
ada_language_server --config=<FILE>
with 'dumb' language clients.I thought I could easily work on it and publish a PR but building ALS on Windows is not documented. I tried using Alire but this builds a non working executable (see issue #1103).
The text was updated successfully, but these errors were encountered: