From mboxrd@z Thu Jan 1 00:00:00 1970 Path: main.gmane.org!not-for-mail From: Hrvoje Niksic Newsgroups: gmane.emacs.devel Subject: Re: new text property Date: Tue, 11 Jun 2002 22:40:56 +0200 Sender: emacs-devel-admin@gnu.org Message-ID: References: <1023607376.8184.1228.camel@space-ghost> <87adq3jp5y.fsf@tc-1-100.kawasaki.gol.ne.jp> <1023735066.26240.14.camel@space-ghost> <1023824830.26240.84.camel@space-ghost> NNTP-Posting-Host: localhost.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: main.gmane.org 1023828151 16678 127.0.0.1 (11 Jun 2002 20:42:31 GMT) X-Complaints-To: usenet@main.gmane.org NNTP-Posting-Date: Tue, 11 Jun 2002 20:42:31 +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 17HsTH-0004Kt-00 for ; Tue, 11 Jun 2002 22:42:31 +0200 Original-Received: from fencepost.gnu.org ([199.232.76.164]) by quimby.gnus.org with esmtp (Exim 3.12 #1 (Debian)) id 17Hsql-0000fE-00 for ; Tue, 11 Jun 2002 23:06:47 +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 17HsSr-0007n0-00; Tue, 11 Jun 2002 16:42:05 -0400 Original-Received: from 212-84-246-077.trmd.net ([212.84.246.77] helo=florida.munich.redhat.com) by fencepost.gnu.org with esmtp (Exim 3.34 #1 (Debian)) id 17HsRm-0007ba-00 for ; Tue, 11 Jun 2002 16:40:58 -0400 Original-Received: from hniksic by florida.munich.redhat.com with local (Exim 3.35 #1 (Debian)) id 17HsRk-0002FI-00; Tue, 11 Jun 2002 22:40:56 +0200 Original-To: emacs-devel@gnu.org, xemacs-design@xemacs.org X-Attribution: Hrvoje X-Face: &{dT~)Pu6V<0y?>3p$;@vh\`C7xB~A0T-J%Og)J,@-1%q6Q+, gs<-9M#&`I8cJp2b1{vPE|~+JE+gx;a7%BG{}nY^ehK1"q#rG O,Rn1A_Cy%t]V=Brv7h (Colin Walters's message of "11 Jun 2002 15:47:10 -0400") Original-Lines: 43 User-Agent: Gnus/5.090006 (Oort Gnus v0.06) XEmacs/21.4 (Common Lisp, i686-pc-linux) 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:4765 X-Report-Spam: http://spam.gmane.org/gmane.emacs.devel:4765 Colin Walters writes: > 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; But in my view, that convenience does not outweigh the need for consistency. Respecting `M-x font-lock-mode', but not any other font-lock variable, is quite inconsistent. >> I would expect things like `font-lock-maximum-size' to keep >> working. > > Why? Because I `M-x font-lock-mode' worked just fine. Because `C-h f font-lock-mode' claims it does. > There is no slowdown when using `font-lock-face'. I never claimed that, sorry if that was unclear. Read the whole of my paragraph, which you broke down in two pieces. It's all about consistency between `M-x font-lock-mode' and the rest of the font-lock-* setup (where font-lock-maximum-size is but one element), which would be broken. >> 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. Exactly. That's one more reason why I think it's not a good idea to merge font-lock and other highlighting on the surface. Again, I don't have strong feelings about this. If many users request this feature, I will not veto its inclusion.