EmEditor (text editor) Forum Index EmEditor Core Bug Reports
Find in files gives up at line 6,238,810 out of 110,116,903 lines | Register To Post |
| Threaded | Newest First | Previous Topic | Next Topic | Bottom |
| Poster | Thread |
|---|---|
| abstract | Posted on: 12/16/2010 5:23 am |
Just popping in ![]() ![]() Joined: 12/16/2010 From: Posts: 2 |
Find in files gives up at line 6,238,810 out of 110,116,903 lines I'm using Find in Files to search one very big log file.
The search string (no escapes, no regular expression) definitely exists below line 6,238,810. Emeditor doesn't even seem to be trying to search that part of the file that's not in memory (it stops searching much too quickly to have loaded the file (some 9Gb) from disk). I don't get any errors, emeditor just refuses to search the file below that line. Version 10.0.4 |
| Yutaka | Posted on: 12/16/2010 12:11 pm |
Webmaster ![]() ![]() Joined: 9/28/2006 From: Redmond Posts: 2401 |
Re: Find in files gives up at line 6,238,810 out of 110,116,903 lines Currently, EmEditor doesn't support Find in Files in very large files. It should display "...: failed to open" message, and continues to the next file.
However, I have just found one bug. I will fix this on the next minor version. Thank you,
|
| abstract | Posted on: 12/17/2010 12:31 am |
Just popping in ![]() ![]() Joined: 12/16/2010 From: Posts: 2 |
Re: Find in files gives up at line 6,238,810 out of 110,116,903 lines Appears to have searched the top of the file. Didn't see "failed to open" though I have before.
Find in very large files would be useful. Whilst on the subject "find in this file" would be useful; i.e. showing the matching lines and hyperlinks back to a loaded file. So providing the same output as "find in files" but applied to a particular, already open file. Keep it up, very good tool. Thanks. |
| CrashNBurn | Posted on: 12/17/2010 2:48 am |
Just can't stay away ![]() ![]() Joined: 4/8/2010 From: Posts: 130 |
Re: Find in files gives up at line 6,238,810 out of 110,116,903 lines Could be done, with Grep. Even an option in EmEditor to parse the file by Grep instead of attempting to load the whole thing. Though could be a hassle to interface with a line-command tool.
An alternative option might be to be able to display/load the saved-output from grep in EmEditor's Output bar/plugin. |
| Threaded | Newest First | Previous Topic | Next Topic | Top |
| Register To Post | |





