Shell environment can't detect current directory being removed and recreated about fish-shell

[faho]

Commands like brew install no longer work as the shell believes there's no current working directory

No, brew (or whatever a "shell-init" is) doesn't believe there is. The error message you get comes from that, not fish.

And like you see, both ls (another external command) and fish's builtin pwd handle this just fine, brew is pretty harsh and refuses to run a command that probably doesn't need the working directory, so they want you to cd ..

There isn't really a way to handle this for fish that doesn't involve opening the working directory on every command, which doesn't sound like a great use of resources.

This is with fish 3.3.1 using macOS Sonoma.

Sidenote: fish 3.3.1 is 15% of all commits ever made to fish behind (counting up to the last release). Please upgrade if you wish to report an issue.

[alxhill]

Both ls and pwd "work" even if the current directory has been deleted, so I figured they were doing something else. brew is not the only tool that broke in this case, but it was the only one I had logs handy for - plus the shell-init error made me think it could be a shell thing. Anyway, thanks for taking a look!

I've verified the same behavior occurs on fish 3.7.0 fwiw.