From: maxwell <ma...@um...> - 2010-04-29 21:15:32
|
On Thu, 29 Apr 2010 15:55:20 -0500, Sarah Cranston <cra...@gm...> wrote: > I happened to install jEdit on a VM and edit a file that is usually pretty > slow over there, and it wasn't slow at all. Is this an XML file? FWIW, I tried to edit a 700,000 line XML file (it's a dictionary) in jEdit 4.3.1 the other day. It loaded fine, but when I tried to jump to the end of the file, jEdit froze, and still appeared to be frozen two hours later. I killed jEdit, and re-started it. But before I went anywhere in that file, I turned off all the "Auto parsing settings" in the SideKick plugin. Now I can jump to the end of the file the first time in five seconds or so, and after that virtually instantaneously. Every line in this file is an open or close tag, or a complete element, so there must be several 100k elements in the file. I'm not surprised SideKick takes awhile to digest it. I do notice, however, that even with SideKick's auto parsing turned off, I can still put the cursor on the beginning or end tag of the root XML element, and jump to its mate with "go to matching tag or bracket", in under a second. So in some sense jEdit still *has* parsed the entire file. Which makes me wonder what it is that SideKick is doing besides parsing the XML. Mike Maxwell |