From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Colin Walters Newsgroups: gmane.emacs.devel Subject: Re: new text property Date: 11 Jun 2002 15:47:10 -0400 Sender: emacs-devel-admin@gnu.org Message-ID: <1023824830.26240.84.camel@space-ghost> References: <1023607376.8184.1228.camel@space-ghost> <87adq3jp5y.fsf@tc-1-100.kawasaki.gol.ne.jp> <1023735066.26240.14.camel@space-ghost> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain Content-Transfer-Encoding: 7bit X-Trace: main.gmane.org 1023825098 2990 127.0.0.1 (11 Jun 2002 19:51:38 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 11 Jun 2002 19:51:38 +0000 (UTC) Return-path: Original-Received: from quimby.gnus.org ([80.91.224.244]) by main.gmane.org with esmtp (Exim 3.33 #1 (Debian)) id 17Hrg2-0000lz-00 for ; Tue, 11 Jun 2002 21:51:38 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17Hs3V-0007wK-00 for ; Tue, 11 Jun 2002 22:15:53 +0200 Original-Received: from localhost ([127.0.0.1] helo=fencepost.gnu.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17Hrfg-0001cy-00; Tue, 11 Jun 2002 15:51:16 -0400 Original-Received: from monk.debian.net ([216.185.54.61] helo=monk.verbum.org) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17HrfB-0001af-00 for ; Tue, 11 Jun 2002 15:50:45 -0400 Original-Received: from space-ghost.verbum.private (freedom.cis.ohio-state.edu [164.107.60.183]) (using TLSv1 with cipher EDH-RSA-DES-CBC3-SHA (168/168 bits)) (Client CN "space-ghost.verbum.org", Issuer "monk.verbum.org" (verified OK)) by monk.verbum.org (Postfix (Debian/GNU)) with ESMTP id 65FB574000BA; Tue, 11 Jun 2002 15:50:34 -0400 (EDT) Original-Received: by space-ghost.verbum.private (Postfix (Debian/GNU), from userid 1000) id 22B7A91EE76; Tue, 11 Jun 2002 15:47:10 -0400 (EDT) Original-To: emacs-devel@gnu.org, xemacs-design@xemacs.org In-Reply-To: X-Mailer: Ximian Evolution 1.0.3 Errors-To: emacs-devel-admin@gnu.org X-BeenThere: emacs-devel@gnu.org X-Mailman-Version: 2.0.9 Precedence: bulk List-Help: List-Post: List-Subscribe: , List-Id: Emacs development discussions. List-Unsubscribe: , List-Archive: Xref: main.gmane.org gmane.emacs.devel:4763 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4763 On Tue, 2002-06-11 at 07:40, Hrvoje Niksic wrote: > Other highlighting mechanims have speed issues as well. For example, > Gnus prefers not to highlight huge messages because that would take > too long. If I controled that with `M-x font-lock-mode' (which would > buy me nothing in turns of convenience; Gnus has variables to > fine-tune its highlighting), It would be convenient because it is the same interface that one uses to enable and disable fontification in many prominent Emacs modes; specifically, I'm thinking of C and Lisp mode buffers, although there are plenty of other examples. Otherwise, to disable/enable highlighting, you have to track down one of those variables, change it, and then recreate the buffer somehow so the change in the variable takes effect. Just typing 'M-x font-lock-mode' is tons easier. > I would expect things like > `font-lock-maximum-size' to keep working. Why? There is no slowdown when using `font-lock-face'. For what other possible reason would you set `font-lock-maximum-size' other than speed? > Plus, font-lock-maximum-decoration is not only about speed. Some > people don't *like* too much decoration. Well, that's a hard problem to solve. Note that even not all modes which use "traditional" font-lock supply multiple levels of keywords, which `font-lock-maximum-decoration' needs.