Bug 90136 - emacs font-lock error on java file
Summary: emacs font-lock error on java file
Status: CLOSED DUPLICATE of bug 90135
Alias: None
Product: Red Hat Linux
Classification: Retired
Component: emacs   
(Show other bugs)
Version: 9
Hardware: All
OS: Linux
Target Milestone: ---
Assignee: Jens Petersen
QA Contact: Brock Organ
Depends On:
TreeView+ depends on / blocked
Reported: 2003-05-03 05:07 UTC by Need Real Name
Modified: 2007-04-18 16:53 UTC (History)
0 users

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Last Closed: 2006-02-21 18:52:52 UTC
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)

Description Need Real Name 2003-05-03 05:07:28 UTC
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.2.1) Gecko/20030225

Description of problem:
$ cat Test1.java
public class Test1 {
  public static void main(String[] args) {

$ emacs -nw -q --no-site-file \
--eval '(global-font-lock-mode t)' \
--eval '(setq debug-on-error t)' Test1.java

This results in the error:
Debugger entered--Lisp error: (wrong-type-argument integer-or-marker-p nil)
  eval((goto-char (match-beginning 4)))
  font-lock-fontify-keywords-region(1 119 nil)
  font-lock-default-fontify-region(1 119 nil)
  font-lock-fontify-region(1 119)
  run-hook-with-args(font-lock-fontify-region 1 119)
  jit-lock-fontify-now(1 501)

This seems to happen with any java file. (the above file is just a simple
sample)  The -nw option is not necessary, I just specify it to make sure that
the problem is not due to some X font problem.  This problem resulted after an
upgrade from rh 8.0 to rh 9.

Version-Release number of selected component (if applicable):

How reproducible:

Comment 1 Need Real Name 2003-05-03 06:08:16 UTC
Whoops.  I accidentally did a double commit.

*** This bug has been marked as a duplicate of 90135 ***

Comment 2 Red Hat Bugzilla 2006-02-21 18:52:52 UTC
Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

Note You need to log in before you can comment on or make changes to this bug.