> with-local-quit is actually documented to allow this sort of
> foreground quitting,

AFAIK it's not just documented to allow that, but it's designed
specifically for that.

> but since the interactive C-g race is unavoidable, we should deprecate
> use of with-local-quit for this purpose.

I tend to agree.

> This change adds a new inhibit-quit-override flag.

Sounds like an arm's race: then we'll have to add
a with-local-quit-override-override, etc...

> +behaves as if 'inhibit-quit' were t.  This change prevents
> +with-local-quit from accidentally allowing quits inside process
> +filters, redisplay callbacks, and other special contexts.

I'm not really familiar with those accidental cases.
Maybe they can be fixed more directly by not using with-local-quit?

Are there bug#NNN where these are discussed?


        Stefan