[Top][All Lists]

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: Network security manager

From: Eli Zaretskii
Subject: Re: Network security manager
Date: Wed, 19 Nov 2014 17:56:06 +0200

> From: Stefan Monnier <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Wed, 19 Nov 2014 08:40:54 -0500
> >> > 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.

It's not clear to me at all.  Some code could set the variable for
reasons that have no relation to prompts.

reply via email to

[Prev in Thread] Current Thread [Next in Thread]