Elizabeth

A niche use-case I've run into this issue with is my [ULID plugin](https://github.com/lizclipse/nu_plugin_ulid), as ULIDs are just `u128`s with the random portion being 80 bits of that. When parsing out...

Well, theoretically you can do something like ``` ssh remote "/opt/homebrew/bin/nu --config $nu.config-path --env-config $nu.env-path -c 'print $env.PATH'" ``` but it doesn't support quite the same syntax and is not...

I've just re-tested this, and it seems in the last version or 2 it's been fixed! At least on macOS & Arch Linux, nu seems to work fine as the...

I've tested this again and it looks like the explicit `ssh remote -t '$env.PATH'` is still broken (my mistake), but I can't figure out a way to force the new...

The issue is that login shells are brought up without any arguments from my understanding, so there isn't a way to force the `-l` option when executing a command via...

I've written a little workaround for this in case someone else is having the same issue: ```nushell export def ssh-exec [host: string, cmd: string --tty (-t), ...rest: string]: nothing ->...

A while ago I did figure out a better workaround that's still not ideal - I have a script called `~/.local/bin/nu-login` with the following contents: ```sh #!/bin/sh if [ -f...

While this might need input from others, my view is that the root cause is that nushell does not implicitly enable `--login` when run as the user's login shell, and...