nix-shell in shebang fails if script name has a space or other shell metacharacters

[lilyball]

Describe the bug

If my script name has a space in it, using nix-shell as a shebang fails as it doesn't escape the space. This also happens if the name contains other shell metacharacters, such as foo{1,2}.sh, but a space is the most common way to reproduce this.

Steps To Reproduce

Create a new file named foo bar.sh with the contents:

#!/usr/bin/env nix-shell
#!nix-shell -i bash -p bash
echo test

Mark it as executable and then execute it (or just pass it to nix-shell directly).

Expected behavior

It should execute and echo test.

Actual behavior

> ./foo\ bar.sh
bash: ./foo: No such file or directory

nix-env --version output

nix-env (Nix) 2.3.7

[lilyball]

This also happens if the script filename is fine but exists in a directory with such characters, and the script is executed using a path that includes the directory name.