Jump to content

Visual Studio Code: Difference between revisions

Visual Studio Code (view source)

Revision as of 02:20, 5 June 2024

1,367 bytes added ,  5 June
m
Fix typo.
VisualWikitext
imported>Dezren39
(update for latest vscode insider issues)
m (Fix typo.)
 
(12 intermediate revisions by 7 users not shown)
Line 37: Line 37:
Some examples here: [https://github.com/search?q=extensionFromVscodeMarketplace&type=code GitHub search for "extensionFromVscodeMarketplace"]
Some examples here: [https://github.com/search?q=extensionFromVscodeMarketplace&type=code GitHub search for "extensionFromVscodeMarketplace"]


{{ic|extensionsFromVscodeMarketplace}} is a manual way to fetch extensions. However, to keep updated from upstream, [https://github.com/nix-community/nix-vscode-extensions nix-community/nix-vscode-extensions] provides the Nix expressions for the majority of available extensions from Open VSX and VSCode Marketplace. A GitHub Action updates the extensions daily.
Note: For fetching the sha256 string you can use the following command. Make sure to replace the author, the package name and version!<syntaxhighlight lang="bash">
nix-prefetch-url https://marketplace.visualstudio.com/_apis/public/gallery/publishers/ms-vscode-remote/vsextensions/remote-ssh-edit/0.47.2/vspackage
</syntaxhighlight>{{ic|extensionsFromVscodeMarketplace}} is a manual way to fetch extensions. However, to keep updated from upstream, [https://github.com/nix-community/nix-vscode-extensions nix-community/nix-vscode-extensions] provides the Nix expressions for the majority of available extensions from Open VSX and VSCode Marketplace. A GitHub Action updates the extensions daily.


It's also possible to install VS Code via [[Home Manager]]:
It's also possible to install VS Code via [[Home Manager]]:
Line 103: Line 105:
});
});
</syntaxHighlight>
</syntaxHighlight>
==== Updating insiders placeholder <code>sha256</code>: ====


You will need to update the placeholder <code>sha256</code> value for each new Insiders build.
You will need to update the placeholder <code>sha256</code> value for each new Insiders build.
Line 108: Line 113:
The new value will appear in a validation error when you try to build.
The new value will appear in a validation error when you try to build.


Example:
Put an arbitrary placeholder value in the <code>sha256</code> field, try to build and you'll get an error message regarding the sha256 value.


Put an arbitrary placeholder value in the <code>sha256</code> field, try to build and you'll get an error message regarding the sha256 value.


If the error examples begin <code>sha256:</code> follow these instructions:
===== If insiders error contains <code>sha256:</code>, follow these instructions: =====


<pre>
<pre>
Line 124: Line 128:
Take that last line and input it where your placeholder was,  'sha256:' in the beginning should be removed.
Take that last line and input it where your placeholder was,  'sha256:' in the beginning should be removed.


If the error examples begin <code>sha256-</code> follow these instructions:
 
===== If insiders error contains <code>sha256-</code>, follow these instructions: =====


<pre>
<pre>
Line 144: Line 149:


Take the output from this command and input it where your placeholder was.
Take the output from this command and input it where your placeholder was.
== Creating development environments using nix-shell ==
Instead of using configuration.nix to add packages (e.g. Python or NodeJS) for developing code on VSCode, you can instead use nix-shell. This will allow you to seamlessly create development environments with the correct packages for your project, without rebuilding and restarting NixOS. See [[Development_environment_with_nix-shell | this page]] for further instructions in building nix-shell development environments.
=== Automatically switch nix shells when switching projects ===
You can do this by using [https://github.com/nix-community/nix-direnv nix-direnv] and [https://marketplace.visualstudio.com/items?itemName=mkhl.direnv the VSCode extension direnv] for integration. View the nix-direnv github page linked for a guide on setting it up.
=== Alternative for manually switching shells ===
The extension [https://marketplace.visualstudio.com/items?itemName=arrterian.nix-env-selector nix-env-selector] will make switching between different nix-shell environments within VSCode so you can switch between different coding projects easily and manually. It has a guide for setting up nix-shell environments for VSCode.


== Wayland ==
== Wayland ==
Line 222: Line 236:
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
{{file|/etc/nixos/configuration.nix|nix|<nowiki>
   programs.nix-ld.enable = true;
   programs.nix-ld.enable = true;
  environment.variables = {
      NIX_LD_LIBRARY_PATH = lib.makeLibraryPath [
        pkgs.stdenv.cc.cc
      ];
      NIX_LD = lib.fileContents "${pkgs.stdenv.cc}/nix-support/dynamic-linker";
  };
</nowiki>}}
</nowiki>}}


Then run <code>nixos-rebuild switch</code> to enable <code>nix-ld</code>. Unlike the <code>nix-vscode-server</code> solution, the <code>nix-ld</code> solution also enables VSCode extensions even if they include non-Nix binaries.  
Then run <code>nixos-rebuild switch</code> to enable <code>nix-ld</code>. Unlike the <code>nix-vscode-server</code> solution, the <code>nix-ld</code> solution also enables VSCode extensions even if they include non-Nix binaries.


=== Nix-sourced VS Code to NixOS host ===
=== Nix-sourced VS Code to NixOS host ===
Line 238: Line 246:
== Remote WSL ==
== Remote WSL ==


Similar to SSH hosts, both <code>nix-vscode-server</code> and <code>nix-ld</code> solution allows a VSCode Windows client to connect a [https://github.com/nix-community/NixOS-WSL NixOS-WSL] host. However, by default the VSCode Windows client uses <code>wsl.exe --exec</code> to start the code server, which bypasses NixOS environment variables required by <code>nix-ld</code>, resulting in failures. As a workaround, add the following settings for the VSCode Windows client:
Similar to SSH hosts, both <code>nix-vscode-server</code> and <code>nix-ld</code> solution allows a VSCode Windows client to connect a [https://github.com/nix-community/NixOS-WSL NixOS-WSL] host. However, by default the VSCode Windows client uses <code>wsl.exe --exec</code> to start the code server, which bypasses NixOS environment variables required by <code>nix-ld</code>, resulting in failures.  
 
 
As a workaround, search for the following text in all files under the directory <code>$HOME\.vscode\extensions\</code>


{{file|%USERPROFILE%\AppData\Roaming\Code\User\settings.json|json|<nowiki>
{{file|wslDaemon.js|js|<nowiki>
{
.push("sh","-c"
    "remote.WSL2.connectionMethod": "localhost"
</nowiki>}}
}
 
 
Replace it with


{{file|wslDaemon.js|js|<nowiki>
.push("sh","-l","-c"
</nowiki>}}
</nowiki>}}
Then restart VS Code and your VS Code client should be able to connect to NixOS host


See https://github.com/nix-community/NixOS-WSL/issues/222 for the discussion about <code>wsl --exec</code> issue on NixOS-WSL.
See https://github.com/nix-community/NixOS-WSL/issues/222 for the discussion about <code>wsl --exec</code> issue on NixOS-WSL.
 
See https://github.com/microsoft/vscode-remote-release/issues/8305#issuecomment-1661396267 about the workaround.
== Using nix-shell ==
Some features of VS Code, like the Python package, require linters or other dependencies. The package [https://marketplace.visualstudio.com/items?itemName=arrterian.nix-env-selector nix-env-selector] makes this easy and does not require overrides on VS Code itself to add dependencies.


== Troubleshooting ==
== Troubleshooting ==
Line 314: Line 329:
fi
fi
</syntaxHighlight>
</syntaxHighlight>
[[Category:Applications]]
Prince213
1

edit

Retrieved from "https://wiki.nixos.org/wiki/Special:MobileDiff/6061...13063"