bug-gnu-emacs
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

bug#3068: marked as done (highlight-lines-matching-regexp doesn't work a


From: Emacs bug Tracking System
Subject: bug#3068: marked as done (highlight-lines-matching-regexp doesn't work after reverting a buffer)
Date: Thu, 23 Apr 2009 01:45:04 +0000

Your message dated Wed, 22 Apr 2009 21:38:42 -0400
with message-id <address@hidden>
and subject line Re: highlight-lines-matching-regexp doesn't work after 
reverting a buffer
has caused the Emacs bug report #3068,
regarding highlight-lines-matching-regexp doesn't work after reverting a buffer
to be marked as done.

This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
bug report if necessary, and/or fix the problem forthwith.

(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact address@hidden
immediately.)


-- 
3068: http://emacsbugs.donarmstrong.com/cgi-bin/bugreport.cgi?bug=3068
Emacs Bug Tracking System
Contact address@hidden with problems
--- Begin Message --- Subject: highlight-lines-matching-regexp doesn't work after reverting a buffer Date: Tue, 21 Apr 2009 12:54:05 +0200
highlight-lines-matching-regexp doesn't work as it should after having
reverted a buffer.

Reproduction:
1. Open a text file with any relevant contents.
2. M-x highlight-lines-matching-regexp and highlight something in the file.
3. M-x revert-buffer RET yes RET
4. Now the highlighting is gone, which I can accept, however...
5. M-x highlight-lines-matching-regexp RET RET
6. Nothing is highlighted this second time!




--- End Message ---
--- Begin Message --- Subject: Re: highlight-lines-matching-regexp doesn't work after reverting a buffer Date: Wed, 22 Apr 2009 21:38:42 -0400
> highlight-lines-matching-regexp doesn't work as it should after having
> reverted a buffer.

I've checked in a fix.

(This is actually a manifestation of Bug#635, "Adding font-lock keywords
results in no font-lock at all".  I added a hack to hi-lock-mode to work
around this bug, and the hack can probably be reversed if/when 635 is
fixed.)


--- End Message ---

reply via email to

[Prev in Thread] Current Thread [Next in Thread]