I have a large directory tree containing about a million lines of source code, plus compiled files. I often search this tree to find all occurrences of (say) a certain variable.
I have discovered that TextPad's Find in Files search won't search the whole tree - there is a binary file (called MPARMUPD.SCR, as it happens) in a proprietary format which terminates all Find in Files Searches!
In other words, if this file is present in one of the directories, and matches the "In files" pattern I am searching, then TextPad will always stop searching when it gets to this file, no matter how many other files and/or folders it hasn't searched yet.
Is this a known bug?
To whom should I send a copy of this file (it is only 32k, unzipped) for testing?
Find in Files stops looking when it gets to a certain file
Moderators: AmigoJack, bbadmin, helios, Bob Hansen, MudGuard
I'd suggest 2 tests before you send the file to anyone - in order to find out whether it is the filename or the filecontent:
First: rename the file to something "normal" like "bla.txt".
Does it stop the Find?
Second: store the file somewhere outside the folders to be searched. Put an empty file with that name in the folders.
Does it stop the Find?
First: rename the file to something "normal" like "bla.txt".
Does it stop the Find?
Second: store the file somewhere outside the folders to be searched. Put an empty file with that name in the folders.
Does it stop the Find?
It is the content
What a good idea.
I just did that - it is the content of the file that stops the search.
It would be better if TextPad told you when it encountered the problem, instead of just silently stopping the search!
I just did that - it is the content of the file that stops the search.
It would be better if TextPad told you when it encountered the problem, instead of just silently stopping the search!