Josh Goebel

Got rid of what?

> isn't much use without being able to see the key codes. Keycodes are included in the in-app help system also.

> or add a special wiki parameter to open the API help on the web. I'm being told we had that before - was there a reason it got removed?

> Don't know, we could fix most serious crashes and release 1.0 Can we get WASM into that? I can get back to the PR soon and bump the API...

Personally I think it's nice looking, though probably harms usability _slightly_.

Is this still pending or finished?

> CPU: I7-4770k @RobLoach That's no slouch of a CPU. It's quite possible it's indeed a Firefox issue, but I'm not sure it's a CPU issue - since as stated...

This sounds like perhaps a Firefox problem more than a TIC-80 problem... can we reproduce this now in 2022 with the latest builds of TIC-80 and Firefox?

I feel like this requested behavior is a Linux/Unix-ism - so I think it needs to be behind a compile flag? I definitely don't want the app to hard-quit with...

Also even from a LInux perspective you could make the argument that TIC-80 is a shell... does Ctrl-C with no program running terminate a shell on Linux? On my Mac...