public inbox for speakup@linux-speakup.org
 help / color / mirror / Atom feed
From: "Glenn at home" <GlennErvin@cableone.net>
To: "Speakup is a screen review system for Linux." <speakup@braille.uwo.ca>
Subject: Re: googling tips?
Date: Thu, 4 May 2006 10:06:06 -0500	[thread overview]
Message-ID: <010601c66f8c$44f8d2e0$6a00a8c0@desktop> (raw)
In-Reply-To: <6.1.0.6.2.20060504084117.01a8d630@mailhost.math.wisc.edu>

When I use Google, I usually use just quotes and the plus sign.
For example:
If I was investigating some tips on how much yeast to use for making wine, I 
would use:
"making wine" + yeast
In the above example, the quotes will treat "making wine" as one thing, 
keeping them together, and it will find web pages that also include the word 
yeast, but not necessarily next to the term "making wine".
I know that there a lot of other forms of punctuation to use in a similar 
way, but this has been working pretty good so far.
Glenn
----- Original Message ----- 
From: "John Heim" <jheim@math.wisc.edu>
To: "speakup" <speakup@braille.uwo.ca>
Sent: Thursday, May 04, 2006 8:50 AM
Subject: googling tips?


I'm wondering if anyone would be interested in sharing googling tips. For
instance, when I'm trying to use a tool I've never used before, I google
for "tutorial OR howto <whatever>".

For example, this weekend, I was trying to figure out rsync, so I googled
for "tutorial OR howto rsync". Note that the "OR" is in capitals. That
tells google to use it as a logical operator rather than as a search term.
So google will look for documents with either 'tutorial' or 'howto' and the
word 'rsync'.

But I'm thinking other people might have little tricks they use to find
stuff on google.

Actually, another great tip is just to use google.  I always google before
asking a question here. First of all, it saves time for the readers of this
list. But secondly, you often get more complete answers via google. People
have taken the time to document a lot of these things because of google. In
other words, people create docs so that other people can find them with
google. Naturally, those documents tend to be more complete than what
someone would type in in response to an email question.


_______________________________________________
Speakup mailing list
Speakup@braille.uwo.ca
http://speech.braille.uwo.ca/mailman/listinfo/speakup 



  reply	other threads:[~ UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
 John Heim
 ` Glenn at home [this message]
 ` Sean M McMahon
   ` Steve Holmes
     ` John Heim
       ` hank
         ` Hart Larry
         ` John Heim
       ` Justin Ekis
         ` Sina Bahram
         ` John Heim
 ` Janina Sajka
 Dawes, Stephen

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to='010601c66f8c$44f8d2e0$6a00a8c0@desktop' \
    --to=glennervin@cableone.net \
    --cc=speakup@braille.uwo.ca \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body. 
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).