wondering how you found that 😬

Did a bit more digging into this and the fix doesn't quite work as expected.

Sending Ctrl + C sends the SIGINT signal, however for some reason it sends the SIGTERM signal when the terminal is frozen and the terminal wants to force quit the current session.
However, once the execUI variable that holds an instance of the TUI struct is instantiated, it doesn't honor the context as it has no idea of it, thus ignoring the call to cancel from the created context.WithCancel.

I updated the goroutine that handles the signal to

go func() {
	select {
	case <-c:
		ctxCancel()
		os.Exit(0)
	case <-ctx.Done():
	}
}()

However, this means we always exit automatically after canceling the cotext and I'm not sure this is the right way to go about this. Does anyone have any insight as to the best approach to this?

cc @LawnGnome @Piszmog @eseliger

I got kinda nerd-sniped reading through this... My first thought was: "isn't there a way to abort an io.ReadAll call when a context is cancelled?" and then I found this comment here golang/go#20280 (comment) and quickly copy&pasted&hacked together this: #794

It seems to do what it should do, but not sure about unintended side-effects etc. Just wanted to possibly add something to conversation 🙂

(Also, have to mention this: the reading stops when you hit Ctrl-D, because Ctrl-D sends the EOF value to the application, which means ends the input reading with an empty file. So, another way to avoid the ugly error would be to print to the user "Hit Ctrl-d to abort" or something, when we detect that input is os.Stdin)

Cancel reading from stdin on Ctrl-C

Thanks @mrnugget . Testing it out now and reading the attached issue.

Closing this for now. I'll work with Thorsten on his fix for this problem.