Re: perl mode color highlighting working badly

[Warren L Dodge]

I guess I should say that the original bug gave you a way of reproducing
something similar to what I saw. I can assure you I didn't find the problem
that way. It was just normal use where it occurs.

I knew the file alone wouldn't be enough. So I can try and explain what I do
to see the problems.

I use gnuclient to send files into a running emacs. It spawns a new frame for
the file I edit.

I believe generally the text in the window is properly highlighted at that
time.

So in the file (regress.) I am editing as I type this, I use the PageDown key
and start moving down real fast to what I am looking for. In this case I
found a section where everything was the color of a quoted string except what
was in quotes. That text was what the color of the other stuff should have
been. For about two page downs. Then it all came back to being correct again.

I went back to the top and did a search for the subroutine where I first saw
the problem. It was still colored improperly. Actually it started to be
wrong a couple of lines prior to the subroutine line.

I now type a space character prior to the "sub" and then everything changes
to the right color except for the lines above. I move up to them and type a
space and they are fixed.

For this file of 1570 lines everything will be ok from now on.


For another file (scan_tree_files.pl) of about 4900 lines there are sections
all through the file that come up wrong.

In this file now I get an area where it is colored wrong and type a
space. Nothing happens. I move up and type a space in a properly colored
area. It changes to a wrong color. I keep moving up and "finally" a spot is
found where it goes down through the file and fixes a large section
properly. During this search of the right spot the paren matching may be
wrong also.


I exit and edit the same file again and a whole different section is wrong.

I see the same thing on Linux (2.5Ghz) and Solaris (500Mhz) machines.

It seems to be different if I bring up the file and wait to move to another
area. Waiting 10 secs on the linux machine then moving to the area produces a
different coloring problem then immediately moving.


Then other times I go back and forth in the file editing and it will mess up
a large section again.


Hope this helps. Files available if needed.

>  Cc: address@hidden, address@hidden
>  From: Stefan Monnier <address@hidden>
>  Date: Tue, 25 Oct 2005 14:49:19 -0400
>  MIME-Version: 1.0
>  Content-Type: text/plain; charset=us-ascii
>  
>  > I did back in Sept. I think it is what started this thread with me being
>  > copied on the emails
>  
>  Sorry, I thought you were talking about more than just this one bug.
>  
>  At least, AFAIK the one bug we were discussing is the one where opening
>  a file, then moving then turning on global-font-lock-mode, ends up with
>  misfontified text.  I understand this bug and know of various ways to fix
>  it, but none seem very attractive right now.
>  
>  This can explain the highlighting problems and the indentation problems, but
>  I'm not sure how it explains the "highlight and then dehighlight as you
>  type" you mention.
>  
>  And of course, it doesn't explain the verilog problem.
>  
>  > I can send you one of the files if you would like.
>  
>  I suspect it depends not just on the files but on the usage pattern.
>  If you could describe how you usually open/visit/navigate those files, it
>  may help me understand why you see the problem so often and give me some
>  hint about what kind of fix might be preferable.
>  
>  
>          Stefan
>