This won't work for fish:

$ fish -tilp "env;exit"
fish: invalid option -- 't'

On the upside, bash, zsh, ksh and tcsh support the argument. We also might be able to drop the exit command.

We also might be able to drop the exit command.

Isn't the exit command good to have just in case something block it from exiting? We have no idea what kind of dumb stuff people put in their dotfiles.

Isn't the exit command good to have just in case something block it from exiting? We have no idea what kind of dumb stuff people put in their dotfiles.

I don't think that exit will protect us from such things, but I noticed that when ommitting the exit while in the REPL, it drops me straight out of it for some weird reason:

> require(".")()
Promise { <pending> }
> [6]  + 11363 suspended (tty input)  node

That doesn't happen with exit in place.

@hughrawlinson Can you update to not add t when in fish?

Yep, I'll push a commit later today 😄

Well, that didn't go as expected, it is now bedtime. Sorry! I'll get to it ASAP.

Before merging this, I'd make sure that all shells we supply -t to actually work as expected and execute only the given command. It's not totally clear to me why a command in a shell startup file shouldn't get picked as the chosen command because technically, it would be encountered earlier than the user-supplied command.

ping :)