Lately, I have been using Google's Desktop Search, Google's new search engine for your PC, a lot in my development. It's fast as lightening and very accurate. Most often, I use it to grep source code, like the Perl and PHP source.

Helpfully, it also keeps caches of older versions of my files. For example, the other night I needed to look up a snippet of Perl code, but I forgot which file I put it in. So I fired up the desktop search and found the snippet in one of 37 caches that Google Desktop kept on a constantly changing file. That's right, 37!

How are the rest of you using it?

Last night I even had a dream about the desktop search...

I was back in college and installed it on my PC under a drive that was mapped to the main Unix machine that everyone used. Wouldn't you know?: Google Desktop indexed everyone's Unix account, allowing me to see everybody's files, including pictures of this one graduate student I liked. I never thought I would get to see them!

(For those of you who don't know: Google Desktop can index files under all user accounts on your PC. This feature has caused some privacy concerns.)

Sadly, the desktop search only works on Windows. No Mac or Linux version is available yet. So it was only a dream. ;-)


In reply to Google Desktop as a development tool by jacques

Title:
Use:  <p> text here (a paragraph) </p>
and:  <code> code here </code>
to format your post, it's "PerlMonks-approved HTML":



  • Posts are HTML formatted. Put <p> </p> tags around your paragraphs. Put <code> </code> tags around your code and data!
  • Titles consisting of a single word are discouraged, and in most cases are disallowed outright.
  • Read Where should I post X? if you're not absolutely sure you're posting in the right place.
  • Please read these before you post! —
  • Posts may use any of the Perl Monks Approved HTML tags:
    a, abbr, b, big, blockquote, br, caption, center, col, colgroup, dd, del, details, div, dl, dt, em, font, h1, h2, h3, h4, h5, h6, hr, i, ins, li, ol, p, pre, readmore, small, span, spoiler, strike, strong, sub, summary, sup, table, tbody, td, tfoot, th, thead, tr, tt, u, ul, wbr
  • You may need to use entities for some characters, as follows. (Exception: Within code tags, you can put the characters literally.)
            For:     Use:
    & &amp;
    < &lt;
    > &gt;
    [ &#91;
    ] &#93;
  • Link using PerlMonks shortcuts! What shortcuts can I use for linking?
  • See Writeup Formatting Tips and other pages linked from there for more info.