I open an untitled document, paste some text in, and then bring up the search/replace dialog I notice that it always defaults to searching (and replacing) my entire home directory.
I really think 'Current Document' would be a much better default, for safety.
Also for performance reasons, if you run a regular expression search and then realise its searching your entire home directory, the search tends to beachball TM for a good while, and cant be cancelled easily
On 3 May 2014, at 6:13, Carpii UK wrote:
I open an untitled document, paste some text in, and then bring up the search/replace dialog I notice that it always defaults to searching (and replacing) my entire home directory.
This is when you bring up Edit → Find → Find in Project… (⇧⌘F).
For a document search dialog use Edit → Find → Find… (⌘F).
I really think 'Current Document' would be a much better default, for safety.
Also for performance reasons, if you run a regular expression search and then realise its searching your entire home directory, the search tends to beachball TM for a good while, and cant be cancelled easily
What is “a good while”? Seconds? Tens of seconds? Minutes?
I do not see issues here with folder searching causing beachball and I can abort it instantly, either closing the window (⌘W) or clicking the stop button to the left of the status text.
You mention regular expression search, so presumably you’re not seeing it with regular search? Is it specific regular expressions (as the patterns have varying running time with known pathetic cases)?
This is when you bring up Edit → Find → Find in Project… (⇧⌘F).
For a document search dialog use Edit → Find → Find… (⌘F).
Ahh, got it, thanks.
I've come from an editor where its ⌘F to search, and ⇧⌘F to Search/Replace, which explains why I'm seeing Project search so often
I do not see issues here with folder searching causing beachball and I can abort it instantly, either closing the window (⌘W) or clicking the stop button to the left of the status text.
What is “a good while”? Seconds? Tens of seconds? Minutes?
Its 5 minutes plus while scanning my home dir - I usually end up killing TM so never found out when it becomes responsive again
The reg exp I used was ' ([0-9]){2})'. Its probably because there are some big files in there, or perhaps its just finding so many matches.
But the lock-up is less of an issue really. I never want to search my home dir, and so it was just a side effect of not understanding how to control scope with ⌘F vs ⇧⌘F
Thanks
On 3 May 2014, at 17:03, Carpii UK wrote:
I do not see issues here with folder searching causing beachball […]
Its 5 minutes plus while scanning my home dir - I usually end up killing TM so never found out when it becomes responsive again
The reg exp I used was ' ([0-9]){2})'. Its probably because there are some big files in there, or perhaps its just finding so many matches.
It’s probably the latter — the search itself is threaded, but since UI has to run on the main thread, updating the list of results will affect perceived performance, and with thousands of results, it’ll probably be noticable.
I searched for the same regexp in my home folder and aborted it after ~12,500 matches, it did take a few seconds (of beachball) before it actually responded, though not anywhere near as bad as what you experience.
-
Allan Odgaard -
Carpii UK