Clean up Windows console mode and Unix `termios` state on process exit about cathode

[alexrp]

I'm not actually sure where/when we could safely do this. Even AppDomain.CurrentDomain.ProcessExit isn't really safe since there might be other handlers that expect to be able to use System.Terminal.

[Thraka]

Is it possible to add a method that can be called that resets it? This way I can call it as I know I terminate.

[alexrp]

That sounds reasonable.

[alexrp]

@Thraka For your use case, would it be acceptable if the cleanup method would perform terminal state cleanup and also exit the process immediately after? This would greatly simplify matters in the library since I would not need to care about users calling the cleanup method and then trying to use the library after.

It might look something like this:

static class Program
{
    static void Main(string[] args)
    {
        using (var lifetime = TerminalLifetime.Create())
        {
            // ... work ...

            if (workFailed)
                lifetime.ExitCode = 1; // defaults to zero
        }

        // lifetime.Dispose() called here, cleans up terminal state and exits
    }
}

To simplify this, I'd probably also provide a package that works similarly to DragonFruit, i.e. it generates the real Main for your application, takes care of the TerminalLifetime for you, and calls your entry point method.

---

PS: I know it's been a while since this issue was opened... I'm only now getting around to continuing the project with .NET 6 being out.

[alexrp]

Resolved in 443eff9.

For your use case, would it be acceptable if the cleanup method would perform terminal state cleanup and also exit the process immediately after? This would greatly simplify matters in the library since I would not need to care about users calling the cleanup method and then trying to use the library after.

I'll spin this off into a separate issue.