🚀 go-pugleaf

The first time you hit ^C in gdb, it prints "Quit" and stops
what it's doing. The second time, it exits. This would be fine
if it only did this if the ^C's were typed one after the other,
but it also happens if I use a ^C to abort some long output
("Nooo. I don't want to see that many variables") and then use
one again at some later time (after many other commands have been
typed). It would be nice if typing a command reset the second ^C to just
interrupt the current op again.

There's a bunch of stuff in there now with "quit_flag" and "immediate_quit",
but I'll be jiggered if I understand it.

						Jordan