From: Herbert Euler <herberteuler@hotmail.com>
To: <bug-gnu-emacs@gnu.org>
Subject: bug#4304: Font-lock in cperl-mode is broken
Date: Tue, 1 Sep 2009 12:21:23 +0800 [thread overview]
Message-ID: <BAY143-W181E3E3B91E35C0081E193DAF10@phx.gbl> (raw)
[-- Attachment #1: Type: text/plain, Size: 1600 bytes --]
Package: emacs
Version: 23.0.50
In the newest Emacs HEAD source, font-lock in cperl-mode is broken.
Here are the steps to reproduce the problem:
1. Start emacs:
$ emacs -Q
2. Visit an empty perl file and switch to cperl-mode:
C-x C-f x.pl
M-x cperl-mode
3. Type `print' (no any characters follow the character `t'):
print|
The vertical bar `|' here indicates the cursor. Now the word
`print' is highlighted with face `cperl-nonoverridable-face'.
4. Now that the cursor is after the character `t', type SPC to append
a whitespace character.
print |
This time, the word `print' gets unhighlighted. There is no
property `face' for that word now:
;; Point is in between `print'.
(text-properties-at (point))
==> (fontified t)
Appending more whitespace characters will not call the highlight
back. However, deleting all of the whitespace characters
highlights it again.
print | ;; Type DEL
print| ;; `print' gets highlighted again
And the face property is added back:
;; Point is in between `print'.
(text-properties-at (point))
==> (face cperl-nonoverridable-face font-lock-multiline t fontified t)
The same problem exists for larger Perl programs. This is only a
simple case.
Regards,
Guanpeng Xu
_________________________________________________________________
More than messages–check out the rest of the Windows Live™.
http://www.microsoft.com/windows/windowslive/
[-- Attachment #2: Type: text/html, Size: 2608 bytes --]
next reply other threads:[~2009-09-01 4:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <87vdjmwz0j.fsf@cyd.mit.edu>
2009-09-01 4:21 ` Herbert Euler [this message]
2009-09-13 17:15 ` bug#4304: marked as done (Font-lock in cperl-mode is broken) Emacs bug Tracking System
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=BAY143-W181E3E3B91E35C0081E193DAF10@phx.gbl \
--to=herberteuler@hotmail.com \
--cc=4304@emacsbugs.donarmstrong.com \
--cc=bug-gnu-emacs@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).