"Find in Project" is useful, but can be slow. I guess I've gotten spoiled by Spotlight, Google Desktop, etc.
My request is that TextMate keep the contents of the project indexed for speed. Also, results should come up as a I type. See, for example, WingIDE which manages to do this.
-Chuck
On 26.05.2007, at 16:40, Chuck Esterbrook wrote:
"Find in Project" is useful, but can be slow. I guess I've gotten spoiled by Spotlight, Google Desktop, etc.
My request is that TextMate keep the contents of the project indexed for speed. Also, results should come up as a I type. See, for example, WingIDE which manages to do this.
-Chuck
After the first search, which takes a while, it is almost instantly finding, for me. So I think it is already keeping an index.
Soryu.
PS: My project:
$ du -hs . 48M . $ ls -R|wc -l 6626
On May 26, 2007, at 1:05 PM, Soryu wrote:
After the first search, which takes a while, it is almost instantly finding, for me. So I think it is already keeping an index.
Nah, that's likely the unified/filesystem/vm buffer cache. A wonderful thing, if you've got the RAM; otherwise the thrashing can suck. :-)
(And aren't those 2GB SODIMM modules getting temptingly affordable?)
j.
On 26.05.2007, at 21:52, Cliff Pruitt wrote:
On May 26, 2007, at 10:40 AM, Chuck Esterbrook wrote:
I guess I've gotten spoiled by Spotlight, Google Desktop, etc.
Spoiled by Spotight? What system are you using? One of the new 8 core beasts? Spotlight is slow as mud for me usually on a Core Duo MacBook Pro.
- Cliff
Quicksilver ftw and I have “only” 1.5 GB of RAM on my Powerbook as well. But still Find in Project never seems to lose its speed after the initial run.
Soryu.
On 26/05/2007, at 22:01, Soryu wrote:
Spoiled by Spotight? What system are you using? One of the new 8 core beasts? Spotlight is slow as mud for me usually on a Core Duo MacBook Pro.
Quicksilver ftw and I have “only” 1.5 GB of RAM on my Powerbook as well. But still Find in Project never seems to lose its speed after the initial run.
I have a private theory, that Spotlight is slow on machines with Developer Tools installed, or any other enormous set of text/PDF files. I have both DevTools and lots of txt/doc/pdf files with my work, and Spotlight really slows down on my Powerbook.
On May 26, 2007, at 5:41 PM, Rafał Komorowski wrote:
On 26/05/2007, at 22:01, Soryu wrote:
Spoiled by Spotight? What system are you using? One of the new 8 core beasts? Spotlight is slow as mud for me usually on a Core Duo MacBook Pro.
Quicksilver ftw and I have “only” 1.5 GB of RAM on my Powerbook as well. But still Find in Project never seems to lose its speed after the initial run.
I have a private theory, that Spotlight is slow on machines with Developer Tools installed, or any other enormous set of text/PDF files. I have both DevTools and lots of txt/doc/pdf files with my work, and Spotlight really slows down on my Powerbook.
It is certainly next to unusable for anyone with a network-mounted home directory...
Rafał Komorowski <komor@...> writes:
On 26/05/2007, at 22:01, Soryu wrote:
Spoiled by Spotight? What system are you using? One of the new 8 core beasts? Spotlight is slow as mud for me usually on a Core Duo MacBook Pro.
Quicksilver ftw and I have “only” 1.5 GB of RAM on my Powerbook as well. But still Find in Project never seems to lose its speed after the initial run.
I have a private theory, that Spotlight is slow on machines with Developer Tools installed, or any other enormous set of text/PDF files. I have both DevTools and lots of txt/doc/pdf files with my work, and Spotlight really slows down on my Powerbook.
Personal experience:
DevTools + 12G of papers (mostly pdf) on a Powerbook G4 1.5 with 512M: Spotlight is slow, close to painfully. Quicksilver much better (slowish)
DevTools + 18G of papers (mostly pdf) on a MacBook pro 2.33 with 3G (yay!): Spotlight is as fast as Quicksilver. First time you call Spotlight can be a bit slow to list results (3-5 sec), from the second time on it's very fast, like in Jobs' keynotes. I use Spotlight as an app launcher, would you believe it?
Piero
On 5/27/07, Piero D'Ancona pierodancona@gmail.com wrote:
Personal experience:
DevTools + 12G of papers (mostly pdf) on a Powerbook G4 1.5 with 512M: Spotlight is slow, close to painfully. Quicksilver much better (slowish)
DevTools + 18G of papers (mostly pdf) on a MacBook pro 2.33 with 3G (yay!): Spotlight is as fast as Quicksilver. First time you call Spotlight can be a bit slow to list results (3-5 sec), from the second time on it's very fast, like in Jobs' keynotes. I use Spotlight as an app launcher, would you believe it?
Piero
Yep, I do the same thing (Spotlight as an app launcher).
Yes, TextMate gets faster after the first time as does Spotlight. But Spotlight's first time is faster than TextMate's, and likewise, Spotlight's subsequent times are faster than TextMate's.
Also, I think Spotlight may be displaying results as they come in. TextMate seems to wait until it has completed the search. Improving that could make a difference.
Indexing would too. (The subsequent speedups are likely from operating system level file caching as someone pointed out.)
For reference, I have Core 2 Duo MacBook Pro with 3 GB. These improvements would probably help slower machines with less RAM even more.
-Chuck
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have no problems with the "Find in Project"-performance, even on network drives (as long as they are in the same network). I know it is slow when searching the first time, so i can expect that an go get a cup of tea.
My biggest complaint is that there is still no fast possibility to narrow the search by sub-folders. (I know my controllers are not in vendor...) This is a point where I would like to see some improvement, as constantly creating temp-projects for search reasons is no fun at all.
(Machine is a MacBook Pro with 2.0 Ghz and 2GB RAM... first edition)
Florian
Yep, I do the same thing (Spotlight as an app launcher).
Yes, TextMate gets faster after the first time as does Spotlight. But Spotlight's first time is faster than TextMate's, and likewise, Spotlight's subsequent times are faster than TextMate's.
Also, I think Spotlight may be displaying results as they come in. TextMate seems to wait until it has completed the search. Improving that could make a difference.
Indexing would too. (The subsequent speedups are likely from operating system level file caching as someone pointed out.)
For reference, I have Core 2 Duo MacBook Pro with 3 GB. These improvements would probably help slower machines with less RAM even more.
-Chuck
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
On May 27, 2007, at 12:45 PM, Florian Gilcher wrote:
-----BEGIN PGP SIGNED MESSAGE----- Hash: SHA1
I have no problems with the "Find in Project"-performance, even on network drives (as long as they are in the same network). I know it is slow when searching the first time, so i can expect that an go get a cup of tea.
My biggest complaint is that there is still no fast possibility to narrow the search by sub-folders. (I know my controllers are not in vendor...) This is a point where I would like to see some improvement, as constantly creating temp-projects for search reasons is no fun at all.
I think this feature has been requested several times, but I am not sure whether or not it is planned for TM 2.0. Can anyone comment on that?
(Machine is a MacBook Pro with 2.0 Ghz and 2GB RAM... first edition)
Florian
Yep, I do the same thing (Spotlight as an app launcher).
Yes, TextMate gets faster after the first time as does Spotlight. But Spotlight's first time is faster than TextMate's, and likewise, Spotlight's subsequent times are faster than TextMate's.
Also, I think Spotlight may be displaying results as they come in. TextMate seems to wait until it has completed the search. Improving that could make a difference.
Indexing would too. (The subsequent speedups are likely from operating system level file caching as someone pointed out.)
For reference, I have Core 2 Duo MacBook Pro with 3 GB. These improvements would probably help slower machines with less RAM even more.
-Chuck
_ For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
-----BEGIN PGP SIGNATURE----- Version: GnuPG v1.4.3 (Darwin) Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org
iD8DBQFGWd/X8RlGMqQ8m7oRAtPSAJ48AT4bN4izfhAC/nAbeTe9BGhdsACfUTCY ew7fzC8YiSH/NarivmwpBzU= =Tn6b -----END PGP SIGNATURE-----
For new threads USE THIS: textmate@lists.macromates.com (threading gets destroyed and the universe will collapse if you don't) http://lists.macromates.com/mailman/listinfo/textmate
Cheers, Yi
On 27. May 2007, at 21:55, Yi Qiang wrote:
[...] I think this feature has been requested several times, but I am not sure whether or not it is planned for TM 2.0. Can anyone comment on that?
I believe I have gone on record at least a dozen times saying 2.0 has an improved find in project (folder)…
On 5/27/07, Allan Odgaard throw-away-1@macromates.com wrote:
On 27. May 2007, at 21:55, Yi Qiang wrote:
[...] I think this feature has been requested several times, but I am not sure whether or not it is planned for TM 2.0. Can anyone comment on that?
I believe I have gone on record at least a dozen times saying 2.0 has an improved find in project (folder)…
Thanks.
-Chuck
We've talked about this earlier too,
but projects with big binary files (without extensions, if that matters) seem to get searched even though they are big binaries.
It can be a 10MB+ file that it tries to find stuff in. Sometimes If the machine is really low on ram, I can get an alert in Mate telling me that we're low on ram and that big file cant be opened.
A setting where one could choose to skip searching files > x megs!?
Tried BBEdit, Xcode and searched the same project and they didn't look in that specific file. I know that deciding if the file is text or binary would be tricky, I mean we could have a 100MB+ postscript file, but would be interesting to know what differs betw say TM and xCode here.
/d
On 28. May 2007, at 19:50, David Eriksson wrote:
[...] Tried BBEdit, Xcode and searched the same project and they didn't look in that specific file. I know that deciding if the file is text or binary would be tricky, I mean we could have a 100MB+ postscript file, but would be interesting to know what differs betw say TM and xCode here.
The way TM presently does it is by:
1) check if TM is set as the handler for this file type (in Finder), if so, search it 2) check if the extension is known as a binary or text extension -- all extensions declared in TM’s Info.plist are known text extensions, but you can right-click a file in the project drawer to toggle the type for the clicked file’s extension 3) scan the first 8 KB of the file and check if it is a) valid UTF-8 and b) contains no control characters (i.e. below 0x20) except for tab and carriage return / line feed).
Files w/o extension will thus always pass/fall based on the third check.
When 2.0 is out, it should be easier to see which files TM chokes on based on the new UI, at that time I’ll take input on improving the heuristic, if there are still problems.
-
Allan Odgaard -
Chuck Esterbrook -
Cliff Pruitt -
David Eriksson -
Florian Gilcher -
Gerd Knops -
Jay Soffian -
Piero D'Ancona -
Rafał Komorowski -
Soryu -
Yi Qiang