You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm requesting that the syntax for environment variables be treated the same way for both Windows and Linux variables so that a vhdl_ls.toml can be checked into version control along with a project and work in any OS without modification.
This is mainly for handling vendor libraries that are installed on a machine, and not directly part of the project. See differences highlighted below:
So the decision to separate windows and unix-like systems was made based on #278. However, I think that there should be a more flexible solution. Probably the best way forward would be to use unix-style substitution (i.e., $VARIABLE), but allow the escape char ($) to be dynamically changeable from some config.
I'm requesting that the syntax for environment variables be treated the same way for both Windows and Linux variables so that a vhdl_ls.toml can be checked into version control along with a project and work in any OS without modification.
This is mainly for handling vendor libraries that are installed on a machine, and not directly part of the project. See differences highlighted below:
Windows:
Linux:
It would be ideal if Windows variables could be handled the same way as Linux variables. Thank you.
The text was updated successfully, but these errors were encountered: