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 183025 - [69cat] [ruby][editor] Unable to cursor up using the arrow keys for long lines of SQL.
Summary: [69cat] [ruby][editor] Unable to cursor up using the arrow keys for long line...
Status: RESOLVED WORKSFORME
Alias: None
Product: ruby
Classification: Unclassified
Component: Code (show other bugs)
Version: 6.x
Hardware: PC Linux
: P2 normal (vote)
Assignee: Erno Mononen
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-03-28 19:36 UTC by esmithbss
Modified: 2010-03-29 14:58 UTC (History)
0 users

See Also:
Issue Type: DEFECT
Exception Reporter:


Attachments
DB Seed file in the process of being converted from SQL to ruby seed data (5.23 KB, application/x-ruby)
2010-03-28 19:37 UTC, esmithbss
Details

Note You need to log in before you can comment on or make changes to this bug.
Description esmithbss 2010-03-28 19:36:14 UTC
[ BUILD # : 201003270201 ]
[ JDK VERSION : 1.6.* ]

See attached file for reference.

In the attached file, when I am working within the ruby section, all is well
with the editor.  All cursor keys work, etc...

If I cursor/mouse/move down  to the bottom of the file, when I try to use the
up-arrow cursor key, I am only able to cursor up to the last line in the file
(SQL INSERT statement).  Any additional cursor up keys do nothing.

Similarly, if I cursor into the SQL data from above using the down-arrow keys,
I am unable to cursor up.
Comment 1 esmithbss 2010-03-28 19:37:52 UTC
Created attachment 96114 [details]
DB Seed file in the process of being converted from SQL to ruby seed data
Comment 2 esmithbss 2010-03-28 19:41:59 UTC
It appears that the editor is getting mixed up on the first character (the I of INSERT) and cannot move backwards beyond this.

If you remove the I from the INSERT statement (leaving NSERT), then the cursor can move up a line.
Comment 3 Erno Mononen 2010-03-29 09:25:15 UTC
Unfortunately I can't reproduce even with the attached file and the same build + JDK 6u18, but I'm thinking this likely has to do with the core editor issues in the recent builds. I don't think that all the editor fixes were propagated to build 201003270201, it would be great if you can test this with a later build once available.
Comment 4 esmithbss 2010-03-29 14:53:12 UTC
I just tried in 0329 and it appears to be working there.
My 0327 still fails with this.

I don't know, but I'll mark as Works For Me. for now.  If this comes back, then I'll reopen.
Comment 5 Erno Mononen 2010-03-29 14:58:16 UTC
Thanks for testing this, hopefully it is really fixed now for good. As you know there were severe problems with the core editor last week that impacted basically most of the editor related functionality, so this could well have been caused by those issues.