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: | Externaly modified files break some editor functionality | ||
---|---|---|---|
Product: | editor | Reporter: | ehucka <ehucka> |
Component: | -- Other -- | Assignee: | issues@editor <issues> |
Status: | RESOLVED WONTFIX | ||
Severity: | blocker | ||
Priority: | P3 | ||
Version: | 6.x | ||
Hardware: | All | ||
OS: | All | ||
Issue Type: | DEFECT | Exception Reporter: | |
Attachments: |
ide log fragment
threaddump |
Description
ehucka
2007-06-20 15:03:22 UTC
Created attachment 44066 [details]
ide log fragment
Created attachment 44067 [details]
threaddump
It looks like that you were in the middle of editing a code template when the file was reloaded. The exceptions were thrown from the code templates handler and the reaload operation failed. After that the editor was clearly in some undefined state. I hope I did not modify any template. Or I do not know what do you mean by code template. I simply go to tests root folder in terminal and executed some recursive 'sed' command to replace a text in all java files in the folder. It was not trivial replace I replaced whole try - catch block by a single method call. I meant code templates like 'fori' followed by tab key. When it's expanded it switches editor in a special mode in which you are required to enter code template parameters. It looks like the editor was in that state when the file was externally modified. But I might be wrong. moving opened issues from TM <= 6.1 to TM=Dev Will be resolved LATER, does not look like a frequent issue. NetBeans.org Migration: changing resolution from LATER to WONTFIX |