From: SourceForge.net <no...@so...> - 2007-06-28 07:08:34
|
Plugin Bugs item #1744627, was opened at 2007-06-28 10:08 Message generated for change (Tracker Item Submitted) made by Item Submitter You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1744627&group_id=588 Please note that this message will contain a full copy of the comment thread, including the initial issue submission, for this request, not just the latest update. Category: None Group: None Status: Open Resolution: None Priority: 5 Private: No Submitted By: Shlomy Reinstein (shlomy) Assigned to: Nobody/Anonymous (nobody) Summary: SideKick can't determine mode of current buffer Initial Comment: Whenever the user opens a file using File->Open or by double clicking it in the File System Browser, SideKick fails to find the parser for the file and logs the following message: SideKick: can't determine mode of current buffer Diving into the code, I saw two things that need to be fixed: 1. SideKick tries to find the parser in response to the EditPaneUpdate.BUFFER_CHANGED message, which arrives before the buffer is loaded. Since the buffer is not yet loaded, jEdit hasn't yet determined its mode, this is the reason for the above log message. This is NOT the reason why SideKick fails to parse the newly opened buffer, but it's a redundant message that is logged to the activity log and should be avoided. 2. Once the buffer is loaded, SideKick gets the BufferUpdate.LOADED message, and ignores it if the view associated with the message is different from that of SideKick. For some reason, this message always comes with a "null" view, so jEdit always ignores the message (since the SideKick view is not null). I think this is a bug in jEdit itself, but as a quick workaround can be to add the "bmsg.getView() != null" to the view comparison test. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=565475&aid=1744627&group_id=588 |