From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Stefan Monnier Newsgroups: gmane.emacs.devel Subject: Re: Network security manager Date: Wed, 19 Nov 2014 08:40:54 -0500 Message-ID: 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> NNTP-Posting-Host: plane.gmane.org Mime-Version: 1.0 Content-Type: text/plain X-Trace: ger.gmane.org 1416404493 20782 80.91.229.3 (19 Nov 2014 13:41:33 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Wed, 19 Nov 2014 13:41:33 +0000 (UTC) Cc: larsi@gnus.org, emacs-devel@gnu.org To: Eli Zaretskii Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Wed Nov 19 14:41:25 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 1Xr5Vc-0008Iq-Nr for ged-emacs-devel@m.gmane.org; Wed, 19 Nov 2014 14:41:24 +0100 Original-Received: from localhost ([::1]:58212 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr5Vc-0003qZ-CG for ged-emacs-devel@m.gmane.org; Wed, 19 Nov 2014 08:41:24 -0500 Original-Received: from eggs.gnu.org ([2001:4830:134:3::10]:44817) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr5VI-0003qR-K2 for emacs-devel@gnu.org; Wed, 19 Nov 2014 08:41:12 -0500 Original-Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1Xr5VB-0006Uy-4b for emacs-devel@gnu.org; Wed, 19 Nov 2014 08:41:04 -0500 Original-Received: from chene.dit.umontreal.ca ([132.204.246.20]:33089) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1Xr5VB-0006Ul-0v; Wed, 19 Nov 2014 08:40:57 -0500 Original-Received: from pastel.home (lechon.iro.umontreal.ca [132.204.27.242]) by chene.dit.umontreal.ca (8.14.1/8.14.1) with ESMTP id sAJDesQ0012599; Wed, 19 Nov 2014 08:40:54 -0500 Original-Received: by pastel.home (Postfix, from userid 20848) id 244F562BA; Wed, 19 Nov 2014 08:40:54 -0500 (EST) In-Reply-To: <83ppcj9740.fsf@gnu.org> (Eli Zaretskii's message of "Wed, 19 Nov 2014 05:55:43 +0200") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/25.0.50 (gnu/linux) X-NAI-Spam-Flag: NO X-NAI-Spam-Threshold: 5 X-NAI-Spam-Score: 0 X-NAI-Spam-Rules: 1 Rules triggered RV5130=0 X-NAI-Spam-Version: 2.3.0.9393 : core <5130> : inlines <1541> : streams <1345135> : uri <1835298> X-detected-operating-system: by eggs.gnu.org: Genre and OS details not recognized. X-Received-From: 132.204.246.20 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:177745 Archived-At: >> > 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