Can't exit from chime.exe in Windows

[masak]

On Windows, in Git Bash (a shell I use most of the time), running chime.exe 0.4.0, there's no convenient/standard way to exit chime:

> ^D

(The ^D is not visible after I type it. Nothing happens.)

This method of exiting works, unexpectedly, when running chime.exe 0.4.0 from the built-in Command Prompt:

> ^D

C:\Users\...\chime>

On the Command Prompt in chime, typing ^Z does nothing. Typing ^Z in Git Bash gives the following:

> 2383621 [sig] bash 1772! sigpacket::process: Suppressing signal 18 to win32 process (pid 9964)

>

On the Command Prompt in chime, typing ^C aborts the current prompt and gives a new one. Double-tapping ^C aborts the entire session and gives the DOS prompt back after a short delay. (Although from the spinning blue mouse pointer that results during the delay, I suspect that this is orchestrated by some task supervisor in Windows.)

In Git Bash, ^C does nothing, either once or twice.

However, in both Git Bash and Command Prompt, I can start something long-running — such as (for i 1 100 (prn i)) — and then hit ^C. This exits the chime.exe with an error message; either of these two:

chime.exe: schedule: re-entered unsafely.
   Perhaps a 'foreign import unsafe' should be 'safe'?

chime.exe: internal error: evacuate: strange closure type 65864681
    (GHC version 8.8.2 for x86_64_unknown_mingw32)
    Please report this as a GHC bug:  https://www.haskell.org/ghc/reportabug

The former error is a lot more common, though.

---

Anyway, there's no uniform way to exit chime.exe across shells (Git Bash and Command Prompt) in Windows. I do enjoy ^D in Command Prompt after discovering it; it's convenient. But I still use Git Bash quite a lot, and in that shell the simplest way out is long-running command and ^C during it.

Maybe having a global (bye) function (mentioned in this issue in the other implementation, and with prior art in PicoLisp) would be a nice complement.