This Bugzilla instance is a read-only archive of historic NetBeans bug reports. To report a bug in NetBeans please follow the project's instructions for reporting issues.

Bug 167424 - Line numbers not displayed
Summary: Line numbers not displayed
Status: RESOLVED DUPLICATE of bug 166738
Alias: None
Product: editor
Classification: Unclassified
Component: -- Other -- (show other bugs)
Version: 6.x
Hardware: Macintosh Mac OS X
: P3 blocker (vote)
Assignee: issues@editor
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2009-06-21 14:44 UTC by rakeshv
Modified: 2009-06-22 15:22 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
Screen capture when numbers not enabled (183.24 KB, image/tiff)
2009-06-22 15:11 UTC, rakeshv
Details
Screen capture when numbers are enabled (185.46 KB, image/png)
2009-06-22 15:11 UTC, rakeshv
Details

Note You need to log in before you can comment on or make changes to this bug.
Description rakeshv 2009-06-21 14:44:41 UTC
I am trying out the RC3 release, and noticed that enabling line numbers adds the gutter, but does not show any numbers.  It works fine on 6.5.1.  I am 
running with Java 1.5 (computer too old for 1.6), so that could be the issue.  I know I cannot create new files etc. with 6.7 since I get class not found errors 
related to javax.script.  I am not sure if line numbers also require 1.6 with 6.7
Comment 1 Jiri Prox 2009-06-22 13:15:05 UTC
Can you please attach screenshot?
Comment 2 Jiri Prox 2009-06-22 13:18:35 UTC
Probably duplicate of issue 166738
Comment 3 rakeshv 2009-06-22 15:11:02 UTC
Created attachment 83876 [details]
Screen capture when numbers not enabled
Comment 4 rakeshv 2009-06-22 15:11:45 UTC
Created attachment 83877 [details]
Screen capture when numbers are enabled
Comment 5 rakeshv 2009-06-22 15:17:48 UTC
Yes, this is the same as issue 166738.  I am using Ruby dark colour scheme.  If I switch over to default colour scheme, the line numbers are visible.
Comment 6 Jiri Prox 2009-06-22 15:22:38 UTC
Thanks for additional info, I'm marking this as a duplicate of issue 166738 then


*** This issue has been marked as a duplicate of 166738 ***