Log search doesnt return everything

jgubby · Post by **jgubby** » Mon Oct 31, 2005 12:56 am

When I search in the log viewer for some strings, it doesnt return anything. Or sometimes it returns many less results than I would expect.

For example, if I search only for the character "e", which should appear in pretty much every log file I get 30 results from a total of 201 log files.

I have it set to find by content, and have tried clearing the cache.
Any suggestions? Would someone else care to search for a single likely character and see if this is just me, or a bug?

Thanks
James

superpants312 · Post by **superpants312** » Wed Nov 02, 2005 11:22 pm

I searched for "e" and got 90/153 logs... but I didn't search by content because I didn't know how... haha I think mine just searched for screen names with "e" in them.

Maybe you're not reeeally searching for content, but screen names?

FredAkbar · Post by **FredAkbar** » Thu Nov 03, 2005 1:51 am

I just searched (definitely by content) for 'e' and got 580 out of over 5,000 logs. That's weird; I know that more than a tenth of my logs have the letter 'e' in them, if for no other reason than all my screen names have 'e' in them (FredHope, etc.) and the screen name is printed in the log file.

waffffffle · Post by **waffffffle** » Thu Nov 03, 2005 2:00 am

Trash the Adium cache in Library/Caches/Adium . That solved my problem.

FredAkbar · Post by **FredAkbar** » Thu Nov 03, 2005 2:03 am

After trashing the Adium caches folder, a search for 'e' by content still found only 600 logs out of over 5,000. And jgubby said that he already tried trashing his caches folder as well.

Does it have to do with how Adium changed logging formats at some point, from plain text (or whatever it used) to HTML?

Post by **evands** » Thu Nov 03, 2005 7:28 am

I just hate SearchKit, which is the 10.3 apple searching API.. it does poorly at best. Looking forward to a move to Spotlight with 1.0. There's no telling what's going on behind the scenes for those e's not to hit.

Arenzera · Post by **Arenzera** » Thu Nov 03, 2005 10:55 am

Won't that mean Adium 1.0 will be 10.4 only, or are you using some #ifdef statements?

Kiel :-)

Post by **evands** » Thu Nov 03, 2005 1:11 pm

Arenzera wrote:Won't that mean Adium 1.0 will be 10.4 only, or are you using some #ifdef statements?

Kiel :-)

Guess?

(Coding note: In general, one doesn't use #ifdef is do runtime changes, though due to the way universal builds are done this very specific case means that would be theoreticaly possible for the short run, though we won't use 'em).

Arenzera · Post by **Arenzera** » Thu Nov 03, 2005 2:15 pm

10.4 only? Wow, I imagine that will make some users keen to upgrade! I welcome the idea!

Kiel :-)

Post by **evands** » Thu Nov 03, 2005 9:08 pm

Arenzera wrote:10.4 only? Wow, I imagine that will make some users keen to upgrade! I welcome the idea!

Kiel :-)

No, Adium will be 10.3 and 10.4... there's no reason to arficially shut out 10.3 users for the purpose of a single feature. Runtime version checking is easy (see AIApplicationAdditions in AIUtilities - [NSApp isOnTigerOrBetter]).

alpharuin · Post by **alpharuin** » Fri Nov 04, 2005 1:26 am

Does searching in the log viewer work for logs converted via ichat2adium script? I don't think it works for me.

EDIT

Actually right now its finding absolutely nothing at all.

Post by **evands** » Fri Nov 04, 2005 6:07 am

waffffffle wrote:Trash the Adium cache in Library/Caches/Adium . That solved my problem.