Re: Network security manager

[Stefan Monnier]

>> > I also did some further testing with my patch, and apparently timers do
>> > not set the running_asynch_code variable?  They probably should set
>> > that separate variable, too.  I think.
>> BTW, another existing variable that you could use is `inhibit-quit'.
> That's dangerous, IMO.  Again, it uses a variable not designed for
> this functionality, IOW this could break without notice.

It's definitely not dangerous.  IIUC he needs this info to decide
whether his code can prompt the user or not.  Maybe it won't do the
right thing in 100% of the cases, but it's clear that if inhibit-quit is
non-nil, we're in a context where we shouldn't prompt the user.


        Stefan