nix-shell shebang does not interpret -E relative to script dir

[lilyball]

Describe the bug

When using nix-shell in a shebang, it interprets filenames given to it relative to the script dir, but it interprets the -E flag relative to the cwd. This is rather problematic. I can't think of any reason to want the -E flag interpreted relative to the current dir and doing so means I'm forced to write a deps.nix file to disk next to my script if I need to import some other file at a known path.

More generally, I should be able to replace #!nix-shell deps.nix -i bash with #!nix-shell -E 'import ./deps.nix' -i bash.

Steps To Reproduce

Write a script that looks something like

#!/usr/bin/env nix-shell
#!nix-shell -i bash -E "with import ./deps.nix {}; mkShell { buildInputs = [bash]; }"
echo it works

Expected behavior

It shouldn't matter what my cwd is when I execute this, it should behave the same and import the deps.nix file that lives right next to the script.

Actual behavior

It tries to import ./deps.nix from whatever my cwd is.

nix-env --version output

nix-env (Nix) 2.3.7

[lilyball]

On a related note, relative paths given to -I are interpreted relative to cwd but should also be script-relative when used in a shebang.

[expipiplus1]

I ran into this a couple of days ago too, here is my workaround, a Haskell/Bash polyglot

#! /usr/bin/env bash
{- 2>/dev/null
# vim: set ft=haskell
DIR="$( cd "$( dirname "${BASH_SOURCE[0]}" )" >/dev/null 2>&1 && pwd )"
exec nix-shell \
  "$DIR/shell.nix" \
  --pure \
  --run "runghc $(printf "%q " "$0" "$@")"
-}
-- haskell code...

[nixos-discourse]

This issue has been mentioned on NixOS Discourse. There might be relevant details there:

https://discourse.nixos.org/t/relative-paths-when-using-nix-shell-as-an-interpreter/1180/5

[lilyball]

@expipiplus1 Neat, but in my case I need to support bash, tcl, perl, python, and ruby scripts, and I need a solution that my non-Nix-savvy coworkers can copy&paste, so the polyglot route is kind of problematic.

[stale]

I marked this as stale due to inactivity. → More info

[lilyball]

Still a problem last I checked

[matthewbauer]

PR: #5088

[stale]

I marked this as stale due to inactivity. → More info

[andersk]

Still an issue in Nix 2.8.0.

[DavidDTA]

This is also an issue for positional arguments. The existing behavior directly contradicts the documentation here:

For example, the Python example could have been written as:

#! /usr/bin/env nix-shell
#! nix-shell deps.nix -i python

where the file deps.nix in the same directory as the #!-script contains: