|
From: SourceForge.net <no...@so...> - 2011-11-30 20:16:45
|
Feature Requests item #918301, was opened at 2004-03-17 13:03 Message generated for change (Comment added) made by tvojeho You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350588&aid=918301&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: Tyler Ward (vertigre) Assigned to: Matthieu Casanova (kpouer) Summary: poor performance with large text files and soft wrap Initial Comment: Jedit does a tolerable job of opening medium size text files, but is no match for UltraEdit with large files. if there was a way to easily open very large files, that would be very nice. This is the algorithm I reccomend, though it's just a though. 1) If the file size is over a set limit, go into large file mode. 2) In large file mode, on opening a file, scan through it for newlines and record the position of each newline. 3) Count the lines (number of newlines found) and load up an area around the current text display window, this can be done by seeking to the appropriate spot in the file. For instance, if someone scrolls 2/3 of the way down a million line file, then you need to load in lines around line 670,000, and you conveniently know the offset into the file of the line, because you made a table of it. So you pick your spot, then load in a few thousand lines above and below, using that as the display. Whenever the user gets too close to the edge, refresh it. This is a big task, but something that jedit should consider if it is going to become the ultimate text editor. -Tyler ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2011-11-30 12:16 Message: it is commented out - does this property drive the large buffer dialog? <PROPS> <PROPERTY NAME="wordBreakChars" VALUE=",+-=<>/?^&* " /> <!-- <PROPERTY NAME="contextInsensitive" VALUE="true"/> --> </PROPS> ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2011-11-30 11:51 Message: Does your text.xml file contains this ? <PROPS> <PROPERTY NAME="contextInsensitive" VALUE="true" /> </PROPS> ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2011-11-30 11:41 Message: the edit mode was 'txt' - as I stated in catalog in mode folder for handling *.txt files. ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2011-11-30 11:30 Message: but what was the edit mode used by your file when you opened it ? ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2011-11-30 11:24 Message: Ah, it seems that this is my doing then; when I first started using jedit, I made a copy of 'text' mode, customized the syntax highlighting and renamed it as 'txt' mode which I use as default for text files. ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2011-11-30 11:23 Message: In fact you're right, there is a bug ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2011-11-30 11:06 Message: I don't understand. If the edit mode is text, the dialog do not appear. ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2011-11-30 09:39 Message: Speaking of the large file mode, is there a way to switch off this feature? Seeing that the simple text mode highlighting does not slow the file loading, it is practically useless for text files to show this warning. tvojeho ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2011-11-30 09:34 Message: Yes, that could help in some cases, unfortunately for me most of the time I need to use the soft wrap. At least I have the time to make coffee while opening the larger files ;) tvojeho ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2011-11-30 09:25 Message: Perhaps the "large file mode" should also have an option to disable soft-wrap and not just highlighting. ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2011-11-30 09:18 Message: Soft wrap is expensive, there is no doubt about it. ---------------------------------------------------------------------- Comment By: tvojeho (tvojeho) Date: 2011-11-30 09:06 Message: Hi, I am not sure how much delay the Sidekick is causing because I am not using this plugin, but for me the biggest problem is soft wordwrap. I am running jEdit 5.0 pre version on Win7 on a laptop 2.2 GHz AMD cpu with 4 GB RAM, Sun java 1.6.0_29 and opening a 4 MB text file with soft wrap is a chore. I tried how much difference the syntax highlighting mode makes, and it seems not much. Time for text to load: Word wrap soft, full syntax highlight...1 min 55 secs Word wrap soft, context insensitive syntax highlight...1 min 54 secs Word wrap none, full syntax highlight...0 min 5 secs Word wrap none, context insensitive syntax highlight...0 min 4 secs Regards, tvojeho ---------------------------------------------------------------------- Comment By: Alan Ezust (ezust) Date: 2011-11-29 22:55 Message: jEdit 4.5pre1 now has a large-file mode that kicks in and allows you to pick a faster syntax highlighting mode. This still doesn't prevent sidekick from doing its thing but that's another issue people are looking at now. ---------------------------------------------------------------------- Comment By: Matthieu Casanova (kpouer) Date: 2009-11-02 05:26 Message: moved to feature requests ---------------------------------------------------------------------- Comment By: rletzler (rletzler) Date: 2009-11-01 20:21 Message: jEdit also gives no feedback about progress beyond telling us that 1 i/o operation is in progress, so it is difficult to tell whether it is hard at work opening a huge file or has frozen up. Some kind of prominent percent done text or thermometer display would be quite useful. ---------------------------------------------------------------------- You can respond by visiting: https://sourceforge.net/tracker/?func=detail&atid=350588&aid=918301&group_id=588 |