From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: martin rudalics Newsgroups: gmane.emacs.devel Subject: Re: Patch: Syntax and Hard Newlines Date: Fri, 17 Nov 2006 19:39:18 +0100 Message-ID: <455E01D6.8000909@gmx.at> References: NNTP-Posting-Host: main.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=ISO-8859-15; format=flowed Content-Transfer-Encoding: 7bit X-Trace: sea.gmane.org 1163788791 13106 80.91.229.2 (17 Nov 2006 18:39:51 GMT) X-Complaints-To: usenet@sea.gmane.org NNTP-Posting-Date: Fri, 17 Nov 2006 18:39:51 +0000 (UTC) Cc: rms@gnu.org, monnier@iro.umontreal.ca, emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Fri Nov 17 19:39:46 2006 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by ciao.gmane.org with esmtp (Exim 4.43) id 1Gl8cf-0002k4-JO for ged-emacs-devel@m.gmane.org; Fri, 17 Nov 2006 19:39:33 +0100 Original-Received: from localhost ([127.0.0.1] helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gl8cf-0005Bq-4Q for ged-emacs-devel@m.gmane.org; Fri, 17 Nov 2006 13:39:33 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1Gl8cU-0005Bi-3f for emacs-devel@gnu.org; Fri, 17 Nov 2006 13:39:22 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1Gl8cS-0005Ay-K7 for emacs-devel@gnu.org; Fri, 17 Nov 2006 13:39:21 -0500 Original-Received: from [199.232.76.173] (helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1Gl8cS-0005Ar-8w for emacs-devel@gnu.org; Fri, 17 Nov 2006 13:39:20 -0500 Original-Received: from [213.165.64.20] (helo=mail.gmx.net) by monty-python.gnu.org with smtp (Exim 4.52) id 1Gl8cR-0004w5-Tw for emacs-devel@gnu.org; Fri, 17 Nov 2006 13:39:20 -0500 Original-Received: (qmail invoked by alias); 17 Nov 2006 18:39:18 -0000 Original-Received: from M3086P025.adsl.highway.telekom.at (EHLO [88.117.33.185]) [88.117.33.185] by mail.gmx.net (mp024) with SMTP; 17 Nov 2006 19:39:18 +0100 X-Authenticated: #14592706 User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: de-DE, de, en-us, en Original-To: Herbert Euler In-Reply-To: X-Y-GMX-Trusted: 0 X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: "Emacs development discussions." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Errors-To: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.devel:62398 Archived-At: > All minor modes should use a same value for a variable, either local > or global, to avoid conflicting each other. If the value of a global > variable is changed, all buffers will be affected. Carefully designed > minor modes will not likely do this for a variable that does not > belong to itself, so only the behavior of killing local variables > matters here. A minor mode is certainly incorrect if it doesn't work as intended when `parse-sexp-lookup-properties' is t. A minor is also incorrect if it globally sets `parse-sexp-lookup-properties'. Hence, as you note, only the behavior when killing this variable locally matters. If modes need conflicting values for one and the same variable, they must use a `let' binding. > Because many minor modes may be activated or deactivated in any order, > your method seems to be the only way. But it requires checking every > minor mode, which is a lot of work. :( It would require a minor mode to add a symbol to a list when it is turned on and remove that symbol when it is turned off. I don't think that's a lot of work.