Commandline invokations should fully exit with a non-zero status, on unrecoverable errors

Question

Commandline invokations should fully exit with a non-zero status, on unrecoverable errors

Closed this issue 5 years ago · 3 comments

Currently, if something you do causes an exception to be thrown during a commandline invokation, e.g. giving ivy a bad path, it will print the exception and maybe a stack trace, and then just hang there until you hit C-c.

Instead it should fully exit, with non-zero status.

I believe this will be fixed basically for free when #69 is fixed.

Answer 1 · 2018-05-30T19:53:34.000Z

There are a number of calls to (exit:exit) (from framework and specified in full in frame.rkt), which will probably be of interest to us.

Answer 2 · 2018-05-30T21:21:28.000Z

That is, I think we can change some of them to (exit:on-exit) and then run (exit -1) (or whatever number), to show that we're exiting under an error status.

Answer 3 · 2019-10-31T03:49:18.000Z

In-progress solution in PR #117. Please comment there.