From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Eli Zaretskii Newsgroups: gmane.emacs.devel Subject: Re: Network security manager Date: Wed, 19 Nov 2014 17:56:06 +0200 Message-ID: <83k32r89rd.fsf@gnu.org> References: <87sihg7r73.fsf@alrua-karlstad.karlstad.toke.dk> <87a93oilxl.fsf@lifelogs.com> <87oas4h555.fsf@lifelogs.com> <87a93oh180.fsf@lifelogs.com> <83h9xw9zg3.fsf@gnu.org> <83d28k9yb9.fsf@gnu.org> <83ppcj9740.fsf@gnu.org> Reply-To: Eli Zaretskii NNTP-Posting-Host: plane.gmane.org X-Trace: ger.gmane.org 1416412616 1497 80.91.229.3 (19 Nov 2014 15:56:56 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Nov 2014 15:56:56 +0000 (UTC) Cc: larsi@gnus.org, emacs-devel@gnu.org To: Stefan Monnier Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 19 16:56:51 2014 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([208.118.235.17]) by plane.gmane.org with esmtp (Exim 4.69) (envelope-from ) id 1Xr7cf-00043a-Km for ged-emacs-devel@m.gmane.org; Wed, 19 Nov 2014 16:56:49 +0100 Original-Received: from localhost ([::1]:59208 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7cf-0002Vm-B8 for ged-emacs-devel@m.gmane.org; Wed, 19 Nov 2014 10:56:49 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:57933) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7cA-0001ol-Ig for emacs-devel@gnu.org; Wed, 19 Nov 2014 10:56:24 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr7c5-0006TJ-Bb for emacs-devel@gnu.org; Wed, 19 Nov 2014 10:56:18 -0500 Original-Received: from mtaout28.012.net.il ([80.179.55.184]:53480) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr7c5-0006Sz-2P for emacs-devel@gnu.org; Wed, 19 Nov 2014 10:56:13 -0500 Original-Received: from conversion-daemon.mtaout28.012.net.il by mtaout28.012.net.il (HyperSendmail v2007.08) id <0NFA00D00MSR5300@mtaout28.012.net.il> for emacs-devel@gnu.org; Wed, 19 Nov 2014 17:53:35 +0200 (IST) Original-Received: from HOME-C4E4A596F7 ([87.69.4.28]) by mtaout28.012.net.il (HyperSendmail v2007.08) with ESMTPA id <0NFA003J9MTBSS80@mtaout28.012.net.il>; Wed, 19 Nov 2014 17:53:35 +0200 (IST) In-reply-to: X-012-Sender: halo1@inter.net.il X-detected-operating-system: by eggs.gnu.org: GNU/Linux 2.6.x X-Received-From: 80.179.55.184 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.14 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:177766 Archived-At: > From: Stefan Monnier > Cc: larsi@gnus.org, emacs-devel@gnu.org > 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.