How to remove "Shell terminated too quickly. The window will not be closed automatically."

[opossalite]

How to remove "Shell terminated too quickly. The window will not be closed automatically."

[Yaraslaut]

You can see some info from contour help page :

            [early-exit-threshold UINT]    If the spawned process exits earlier than the given threshold seconds, an error message will be printed and the window not closed immediately.
                                           [default: 6]

This message you see happens only if you try to exit immediately after opening the terminal, so running with contour early-exit-threshold 0 must solve the problem, also, what version of contour are you using?

[opossalite]

Seems to be 0.3.12.262. Adding the early-exit-threshold argument fixes it, thank you. I'm not sure why this threshold exists though, what is the logic behind it being set at 6 seconds?

[Yaraslaut]

Seems to be 0.3.12.262. Adding the early-exit-threshold argument fixes it, thank you. I'm not sure why this threshold exists though, what is the logic behind it being set at 6 seconds?

@christianparpart might tell some story about it, i think that it was introduced on the early stage of development for test purposes.

[christianparpart]

Hi @TheTerrior. This was added because it MAY be that whatever application you spawn as main program in your terminal (usually the shell), can exit right at the startup. This leads to the user believing that the terminal is not working, because you don't see that it even was there, and even if you noticed that, the window would be closed too quickly to actually read any potential diagnostic error message, telling you, why the program terminated too quickly.

Contour since then added a guard that prevents too quick terminating apps to also terminate the terminal in order to allow the user to review the screen before finally closing it.

However, on our CI side, we must expect some tests to terminate quickly, so early-exit-threshold SECONDS was added to to be able to set it to 0, especially since in test-automation, there'll be no user to trigger input of any form, just to finish the integration-test.

Does this clarify its existence for you? Is there anything that you think might help improving user experience?