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
In particular both the compilerPath and includePath I had to add in manually.
My shell.nix brings in $NIX_CFLAGS_COMPILE and $NIX_LDFLAGS which shows us all the include paths we need.
Describe the solution you'd like
It would be nice if nix-env-selector could acquire this information, or allow us to configure it to acquire this information from the relevant nix environment, then provide us a way to reference these "variables" from the shell environment for other VScode extensions such as the C/C++ extension. That would be most flexible way.
I'm not familiar with how vscode extensions work, and how to apply these variables to vscode dynamically, but it would greatly simplify the usage of nix-shell related environment configuration with other extensions and other languages.
The text was updated successfully, but these errors were encountered:
Is your feature request related to a problem? Please describe.
The
c_cpp_properties.json
configuration file is necessary for intellisense to work for C/C++ files.For example right now I have to manually configure it like:
In particular both the
compilerPath
andincludePath
I had to add in manually.My
shell.nix
brings in$NIX_CFLAGS_COMPILE
and$NIX_LDFLAGS
which shows us all the include paths we need.Describe the solution you'd like
It would be nice if
nix-env-selector
could acquire this information, or allow us to configure it to acquire this information from the relevant nix environment, then provide us a way to reference these "variables" from the shell environment for other VScode extensions such as the C/C++ extension. That would be most flexible way.I could imagine doing something like:
I'm not familiar with how vscode extensions work, and how to apply these variables to vscode dynamically, but it would greatly simplify the usage of
nix-shell
related environment configuration with other extensions and other languages.The text was updated successfully, but these errors were encountered: