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.
Summary: | [jVi] AssertionError: Start offset must be less than or equal to the end offset. startOffset = 0, endOffset = -1 | ||
---|---|---|---|
Product: | editor | Reporter: | Marian Mirilovic <mmirilovic> |
Component: | Painting & Printing | Assignee: | err <err> |
Status: | CLOSED FIXED | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
URL: | http://statistics.netbeans.org/exceptions/detail.do?id=85078 | ||
Issue Type: | DEFECT | Exception Reporter: | 85078 |
Description
Marian Mirilovic
2008-10-15 11:24:11 UTC
Ernie, this seems to be in jVi plugin. Is this something that you have been already tracking? Or do you want me to file it in jVi's bugtracking system? Thanks (I've been traveling for a few months, mostly out of touch..., not home until a few weeks) This sounds familiar, think I fixed it before I left, but haven't released it yet. I didn't realize it was being so widely reported. The problem has to do with my original workaround for Issue 114642 . I was automatically subtracting 1 from end offset, but with 6.5 I was getting updates of (0,0) so when I subtracted one from end this error was provoked. The fix simply avoids the subtract in problem situations. Don't know how administrative 3rd party stuff works best. You can [jvi] it and assign to me if that works. Won't release fix till get home. > (I've been traveling for a few months, mostly out of touch..., not home until a few weeks) Wow, lucky you :-)! > The problem has to do with my original workaround for Issue 114642 . Oh, I see, I should finally fix that. > Don't know how administrative 3rd party stuff works best. You can [jvi] it and assign to me if that works. > Won't release fix till get home. I don't know either, so I'll just leave this here and assign it to you. It's not critical, 6.5 is almost out of the door and this is definitely not a showstopper for us. So, feel free to fix it when you have time. Thanks for a quick reply!! > Thanks for a quick reply!! Just lucky. Been camping. Checked into a resort last night. Try to at least read primary inbox when I get a chance. > 6.5 is almost out of the door (I should find the issue's, but...) Did the KeyBindings stuff get changed around? You were talking about a flag/attribute for a binding called "private" or something-or-another, for those that shouldn't be changeable. Since there's been very few jVi bugs reported over the last few months, it looks like the jVi integration must be in pretty good shape (except for this issue). > Did the KeyBindings stuff get changed around? You were talking about a flag/attribute for a binding > called "private" or something-or-another, for those that shouldn't be changeable. No, sorry, I didn't managed to do this. I was pinned down by other high priority bugs and this has been working reasonably well, so I didn't get back to it. > .. it looks like the jVi integration must be in pretty good shape I think it is, there are people here in the office who use jVi plugin and I haven't heard any complaints from them. I'm sure they would come if something was broken. :-) Fix available in nbvi-1.2.0.x26.zip v/c |