[Feature] Pick up nix environment in tasks about nix-env-selector HOT 5 OPEN

Here's an almost transparent workaround:

In .vscode/settings.json:

{
  "terminal.integrated.automationProfile.linux": {
    "path": "${workspaceRoot}/.vscode/nix-shell-or-bash.sh",
    "env": {
      "PROJ_DIR": "${workspaceRoot}"
    }
  }
}

Then, in .vscode/nix-shell-or-bash.sh (don't forget to chmod +x the file!)

#!/bin/sh
echo $PROJ_DIR
shift # ignore the initial -c added by VS Code

# The condition may be wrong because I'm not sure if Nix (!= NixOS) users have this file
if [ -e /run/current-system/sw/bin/nix-shell ]; then
    # A nix-shell is a available
    if [ -e "$PROJ_DIR/.envrc" ]; then
        # Use direnv (usually faster than nix-shell)
        direnv exec $PROJ_DIR $@
    else # TODO you could add an elif for a flake.nix file and launch nix develop instead
        # Use nix-shell
        nix-shell --run "$@"
    fi
else
    # For people not using NixOS
    bash -c "$@"
fi

from nix-env-selector.

Hi @bcardiff the extension doesn't affect tasks for now :(

from nix-env-selector.

What might be an entry point to solve this is the configuration option terminal.integrated.automationShell.linux. But nix-shell is not a POSIX compliant shell i.e. it does not handle -c well. Furthermore is it not possible to specify additional arguments to vscode to handle this. Obviously one can resort to a wrapper, that filters the -c switch and then set this wrapper as the automation shell.

In the meanwhile, the following tasks.json snippet works without this extension.
CAUTION: This snippets assumes, that the nix expression file is called either shell.nix or default.nix:

        {
            "label": "make",
            "type": "shell",
            "linux": {
                "options": {
                    "shell": {
                        "executable": "/run/current-system/sw/bin/nix-shell",
                        "args": [
                            "--run",
                        ],
                    },
                },
            },
            "command": "make",
        },

The VSCode Team seems to focus on terminal profiles. Once these are referencable within tasks, a corresponding task template could be provided by this extension.

from nix-env-selector.

This is a huge pain esp. when dealing with non-type: "shell" tasks. Eg for vscode extension development, the main launch command looks like:

    {
      "name": "Run Extension",
      "type": "extensionHost",
      "request": "launch",
      "args": ["--extensionDevelopmentPath=${workspaceFolder}"],
      "outFiles": ["${workspaceFolder}/out/**/*.js"],
      "preLaunchTask": "${defaultBuildTask}",
    },

from nix-env-selector.

Is there any new workaround for this since the referenced issue has been closed?

from nix-env-selector.