From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Tassilo Horn Newsgroups: gmane.emacs.devel Subject: Re: Need help with search based font-locking Date: Mon, 28 Dec 2009 19:18:01 +0100 Message-ID: <87skavrmhy.fsf@thinkpad.tsdh.de> References: <877hsen0na.fsf@thinkpad.tsdh.de> <87637yj64c.fsf@thinkpad.tsdh.de> <87ljgn8cax.fsf@thinkpad.tsdh.de> NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1262024308 11570 80.91.229.12 (28 Dec 2009 18:18:28 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Mon, 28 Dec 2009 18:18:28 +0000 (UTC) To: emacs-devel@gnu.org Original-X-From: emacs-devel-bounces+ged-emacs-devel=m.gmane.org@gnu.org Mon Dec 28 19:18:21 2009 Return-path: Envelope-to: ged-emacs-devel@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1NPKAe-0007Yt-Ks for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2009 19:18:20 +0100 Original-Received: from localhost ([127.0.0.1]:56420 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPKAe-0001Mx-Fy for ged-emacs-devel@m.gmane.org; Mon, 28 Dec 2009 13:18:20 -0500 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1NPKAZ-0001Mk-Eu for emacs-devel@gnu.org; Mon, 28 Dec 2009 13:18:15 -0500 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1NPKAU-0001M2-Hg for emacs-devel@gnu.org; Mon, 28 Dec 2009 13:18:14 -0500 Original-Received: from [199.232.76.173] (port=37439 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1NPKAU-0001Lz-CS for emacs-devel@gnu.org; Mon, 28 Dec 2009 13:18:10 -0500 Original-Received: from out1.smtp.messagingengine.com ([66.111.4.25]:60447) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1NPKAU-00061k-AL for emacs-devel@gnu.org; Mon, 28 Dec 2009 13:18:10 -0500 Original-Received: from compute2.internal (compute2.internal [10.202.2.42]) by gateway1.messagingengine.com (Postfix) with ESMTP id CCF45C9079 for ; Mon, 28 Dec 2009 13:18:09 -0500 (EST) Original-Received: from heartbeat1.messagingengine.com ([10.202.2.160]) by compute2.internal (MEProxy); Mon, 28 Dec 2009 13:18:09 -0500 DKIM-Signature: v=1; a=rsa-sha1; c=relaxed/relaxed; d=messagingengine.com; h=from:to:subject:in-reply-to:references:date:message-id:mime-version:content-type; s=smtpout; bh=uGa74WjtMy9lrY/4xM5JL24PHdo=; b=prajLlaJ2o2dH3zbei+bNcAoYxNirs3EUgwBETDgp5NOe4NGNZFhI0Gt3a/FAM2k8cX44ckab91vTxUJYFOPbBRQgwaIa5P81YBd/PHuOb26IEzAJnC/AnkQF3UMwDRDBGj8thtfNJtnKrRamPs6DPLcfwYhwdJkhXY+8+KSgcI= X-Sasl-enc: azjzijgYXyMhEGy+1pkNF/cyDwZE6dMsSU+TmirO+Cam 1262024289 Original-Received: from thinkpad.tsdh.de (p54AF2046.dip0.t-ipconnect.de [84.175.32.70]) by mail.messagingengine.com (Postfix) with ESMTPA id E558C49B2EA for ; Mon, 28 Dec 2009 13:18:08 -0500 (EST) In-Reply-To: (Lennart Borgman's message of "Mon, 28 Dec 2009 14:54:51 +0100") User-Agent: Gnus/5.13 (Gnus v5.13) Emacs/23.1.90 (gnu/linux) Mail-Copies-To: never Mail-Followup-To: emacs-devel@gnu.org X-detected-operating-system: by monty-python.gnu.org: Genre and OS details not recognized. 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:118875 Archived-At: Lennart Borgman writes: Hi Lennart, >> What's the reason for disabling `font-lock-mode-hook' while >> deactivating `font-lock-mode', but not while enabling it again? > > Oh, thanks. I should have commented on that in the code. > > It is just because hi-lock is turned off otherwise. But there is a > variable > > hi-lock--inhibit-font-lock-hook > > I could have used too. However I thought there might be other things > behaving similar to hi-lock in this respect. Hm, I think, in that case let-binding `hi-lock--inhibit-font-lock-hook' would be more appropriate, because it's a special case to circumvent the asymmetry of the function `hi-lock-font-lock-hook', which switches off `hi-lock-mode' when `font-lock-mode' is disabled, but doesn't switch it on in the other case. If nobody objects, I'll commit version modified this way. Bye, Tassilo