From mboxrd@z Thu Jan 1 00:00:00 1970 Path: news.gmane.org!not-for-mail From: Harry Putnam Newsgroups: gmane.emacs.help,gmane.emacs.devel Subject: Re: cperl-mode and fontlock Date: Fri, 25 Sep 2009 17:29:45 -0500 Organization: Still searching... Message-ID: <87ab0iodye.fsf@newsguy.com> References: NNTP-Posting-Host: lo.gmane.org Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii X-Trace: ger.gmane.org 1253917848 23099 80.91.229.12 (25 Sep 2009 22:30:48 GMT) X-Complaints-To: usenet@ger.gmane.org NNTP-Posting-Date: Fri, 25 Sep 2009 22:30:48 +0000 (UTC) Cc: emacs-devel@gnu.org To: help-gnu-emacs@gnu.org Original-X-From: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Sat Sep 26 00:30:41 2009 Return-path: Envelope-to: geh-help-gnu-emacs@m.gmane.org Original-Received: from lists.gnu.org ([199.232.76.165]) by lo.gmane.org with esmtp (Exim 4.50) id 1MrJJI-0004Pc-Q0 for geh-help-gnu-emacs@m.gmane.org; Sat, 26 Sep 2009 00:30:41 +0200 Original-Received: from localhost ([127.0.0.1]:45398 helo=lists.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MrJJI-0002Cy-4O for geh-help-gnu-emacs@m.gmane.org; Fri, 25 Sep 2009 18:30:40 -0400 Original-Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MrJIs-0002Cp-Gj for help-gnu-emacs@gnu.org; Fri, 25 Sep 2009 18:30:14 -0400 Original-Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MrJIn-0002Bb-Tl for help-gnu-emacs@gnu.org; Fri, 25 Sep 2009 18:30:13 -0400 Original-Received: from [199.232.76.173] (port=42670 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MrJIn-0002BR-1l for help-gnu-emacs@gnu.org; Fri, 25 Sep 2009 18:30:09 -0400 Original-Received: from lo.gmane.org ([80.91.229.12]:36465) by monty-python.gnu.org with esmtps (TLS-1.0:RSA_AES_256_CBC_SHA1:32) (Exim 4.60) (envelope-from ) id 1MrJIk-0006Q8-EM for help-gnu-emacs@gnu.org; Fri, 25 Sep 2009 18:30:07 -0400 Original-Received: from list by lo.gmane.org with local (Exim 4.50) id 1MrJIh-0004Fy-IN for help-gnu-emacs@gnu.org; Sat, 26 Sep 2009 00:30:03 +0200 Original-Received: from c-98-215-178-110.hsd1.in.comcast.net ([98.215.178.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Sep 2009 00:30:03 +0200 Original-Received: from reader by c-98-215-178-110.hsd1.in.comcast.net with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Sat, 26 Sep 2009 00:30:03 +0200 X-Injected-Via-Gmane: http://gmane.org/ Original-Lines: 94 Original-X-Complaints-To: usenet@ger.gmane.org X-Gmane-NNTP-Posting-Host: c-98-215-178-110.hsd1.in.comcast.net User-Agent: Gnus/5.110011 (No Gnus v0.11) Emacs/23.1.50 (gnu/linux) Cancel-Lock: sha1:zJH+uZCt1Flb2VRFIevXU+wCcWQ= X-detected-operating-system: by monty-python.gnu.org: GNU/Linux 2.6 (newer, 3) X-BeenThere: help-gnu-emacs@gnu.org X-Mailman-Version: 2.1.5 Precedence: list List-Id: Users list for the GNU Emacs text editor List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Original-Sender: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Errors-To: help-gnu-emacs-bounces+geh-help-gnu-emacs=m.gmane.org@gnu.org Xref: news.gmane.org gmane.emacs.help:68478 gmane.emacs.devel:115646 Archived-At: [ALERT - I've attempted cross posting this to devel as well -ED reader@newsguy.com] Ilya Zakharevich writes: > On 2009-09-17, Harry Putnam wrote: >> As I enter code... syn-hilite appears to be working just as expected >> but as time wears on and some of the code scrolls off the screen, >> Eventually when viewed later syn-hilite has disappeared in all but a >> few items. >> >> Just scrolling code off visible area and back doesn't appear to do it >> ... I'm not sure exactly what does. >> >> If I return to edit some already entered code that has lost its >> syn-hilite, the hilite returns the instant I make any >> modification. But then later I see its left again. >> >> Calling M-x `font-lock-fontify-buffer' does not seem to re-instate the >> syntax highlight where it has already gone away either. > ^^^^^ > > What is this "where"? Region of buffers, or buffers as a whole? Sorry, even though english is my first language I speak it with near illiteracy. `where' was supposed to mean any spots in the code where font-locking has already stopped working, are not revivied by M-x font-lock-fontify-buffer. That is, I can see some code with no font-locking visible in current buffer, but it does not get fixed when font-lock-fontify-buffer is run. That isn't quite right either, because some of it does get fixed. Also with the M-x normal-mode seems to re-font-lock something but not others. Very confusing and maddening. If I edit a block where many elements have lost syntax coloring... For a brief while the syntax coloring is re-established near the cursor line. Maybe 2/3 lines in either direction. Another part to this... not sure if its related is that mic-paren-mode is now giving false readings at times... I've never noticed that before. Any (`) backtick between matching parens (even in comments...) might cause a false reading it seems > Just 2 pieces of how I view similar problems: > > a) cperl-mode distributed with RMS Emacs is completely borken. See > "my" versions; This is the version that came with emacs-23: (From top of the file) ;;; cperl-mode.el --- Perl code editing commands for Emacs ;; Copyright (C) 1985, 1986, 1987, 1991, 1992, 1993, 1994, 1995, 1996, 1997, ;; 1998, 1999, 2000, 2001, 2002, 2003, 2004, 2005, 2006, 2007, 2008, 2009 ;; Free Software Foundation, Inc. ;; Author: Ilya Zakharevich ;; Bob Olson ;; Maintainer: Ilya Zakharevich ;; Keywords: languages, Perl ;; This file is part of GNU Emacs. ;; GNU Emacs is free software: you can redistribut... [...] Is there something newer or better available? > > b) I think I have seen things similar to what you describe - about > 5-7 years ago. It appears my version of cperl-mode is not totally outdated eh?. Any other problems that might cause this? something to do with shadow paths or whatever its called? I went to the cperl-mode.el file by calling M-x find-library inside emacs. So, I guess that means that is the one loading... right. Any other input would be greatly appreciated... My coding skills are terrible enough without having syntax coloring problems.