- December 16, 2010 at 2:23 pm #9153
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.4December 16, 2010 at 9:11 pm #9154
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,December 17, 2010 at 9:31 am #9155
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.December 17, 2010 at 11:48 am #9156
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.
You must be logged in to reply to this topic.