You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I probably shoudln't be doing this, but when I use the exit builtin with a negative number, I get an assertion failure. For example, running fish -c 'exit -1' gives:
Another from the "why are we asserting instead of doing something
sensible" department.
The alternative is to make exit() and return() compute their own exit
code, but tbh I don't want any *other* builtin to hit this either?
Fixes#9659
(cherry picked from commit a16abf2)
I probably shoudln't be doing this, but when I use the
exit
builtin with a negative number, I get an assertion failure. For example, runningfish -c 'exit -1'
gives:Note that the crash is in the
fish
that I just spawned to runexit -1
, not the shell used to spawnfish
.Version Information:
fish --version
reportsfish, version 3.6.0
uname -a
reportsLinux DESKTOP-38G9TM7 5.15.90.1-microsoft-standard-WSL2 #1 SMP Fri Jan 27 02:56:13 UTC 2023 x86_64 x86_64 x86_64 GNU/Linux
env HOME=$(mktemp -d)
makes no differenceThe text was updated successfully, but these errors were encountered: