I don't recall this being an issue before, but it seems that the underlying search (IIRC it uses ack?) is no longer ignoring binaries as of build 9491. This is causing the dratted beachball on every search I do in my project, as well as severely polluting the results.
The binary is accessed via a symbolic link, if that matters.
Le 28 oct. 2013 à 21:56, Jason McC. Smith jason@ncpod.org a écrit :
I don't recall this being an issue before, but it seems that the underlying search (IIRC it uses ack?) is no longer ignoring binaries as of build 9491. This is causing the dratted beachball on every search I do in my project, as well as severely polluting the results.
I've seen that one too and forgot to file an issue. I think it started to do this after the encoding support got beefed up. My workaround was to add *.a files to "Ignore files" in the Preferences.
Regards, Etienne Samson -- samson.etienne@gmail.com
On 28 Oct 2013, at 21:56, Jason McC. Smith wrote:
I don't recall this being an issue before, but it seems that the underlying search (IIRC it uses ack?) is
It does not use ack.
no longer ignoring binaries as of build 9491.
Initially it ignored files that were not in UTF-8. It has been a while since that limitation was lifted.
In the most recent builds it tries to figure out what the encoding is of your non-UTF-8 files.
This is causing the dratted beachball on every search I do in my project,
The analysis (for encoding) might cause the search to be slower (it would only be done for non-UTF-8 files).
But it generally should not lead to a beachball, unless you get a lot of results, because the results list is updated on the main (UI) thread.
as well as severely polluting the results.
Do the binary files have a special extension? If so, it would probably make the most sense to add that to the glob in Preferences → Projects → Non-text files. That would also exclude them from the “Go to File” list and should not open them as text, if double-clicked in the file browser.
The binary is accessed via a symbolic link, if that matters.
Not beyond that disabling “follow symbolic links” in the gear menu of the find window would be another workaround (but maybe you do want them followed).
No special extension, it's the executable for unit testing, but I will disable symbolic links for the time being. I think that should do it as a workaround.
With even only a dozen or so results from the binary, the moment it hits that binary in the lower left progress synopsis of the Find panel, blammo, beachball, for a good 60-75 seconds. Whether that's happening in the analysis or the search, I don't know, but the binary is 40MiB.
On Mon, Oct 28, 2013 at 2:39 PM, Allan Odgaard mailinglist@textmate.orgwrote:
On 28 Oct 2013, at 21:56, Jason McC. Smith wrote:
I don't recall this being an issue before, but it seems that the
underlying search (IIRC it uses ack?) is
It does not use ack.
no longer ignoring binaries as of build 9491.
Initially it ignored files that were not in UTF-8. It has been a while since that limitation was lifted.
In the most recent builds it tries to figure out what the encoding is of your non-UTF-8 files.
This is causing the dratted beachball on every search I do in my project,
The analysis (for encoding) might cause the search to be slower (it would only be done for non-UTF-8 files).
But it generally should not lead to a beachball, unless you get a lot of results, because the results list is updated on the main (UI) thread.
as well as severely polluting the results.
Do the binary files have a special extension? If so, it would probably make the most sense to add that to the glob in Preferences → Projects → Non-text files. That would also exclude them from the “Go to File” list and should not open them as text, if double-clicked in the file browser.
The binary is accessed via a symbolic link, if that matters.
Not beyond that disabling “follow symbolic links” in the gear menu of the find window would be another workaround (but maybe you do want them followed).
______________________________**_________________ textmate mailing list textmate@lists.macromates.com http://lists.macromates.com/**listinfo/textmatehttp://lists.macromates.com/listinfo/textmate
On 28 Oct 2013, at 23:11, Jason McC. Smith wrote:
[…] With even only a dozen or so results from the binary, the moment it hits that binary in the lower left progress synopsis of the Find panel, blammo, beachball, for a good 60-75 seconds. Whether that's happening in the analysis or the search, I don't know, but the binary is 40MiB.
If possible, please send the binary and an example search string that produce the bad behavior to tm-support@macromates.com.
-
Allan Odgaard -
Etienne Samson -
Jason McC. Smith