Re: Network security manager

[Ted Zlatanov]

On Wed, 19 Nov 2014 08:40:54 -0500 Stefan Monnier <address@hidden> wrote: 

>>> > 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.

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

Would it work to use the logic of "the buffer that initiated the
connection is in the foreground"? In that case, we could store the
buffer name as an optional record in the process info structure--
`open-network-stream' could figure it out mostly automatically?

Ted