Re: Using Google to find documentation (was Re: naturalize pitches)

[J Martin Rushton]

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Also works with duckduckgo

On 29/03/16 15:56, Knute Snortum wrote:
> Something you can do with Google to find documentation is use the 
> "site:" syntax:
> 
> site:lilypond.org/doc/v2.19 <http://lilypond.org/doc/v2.19> search 
> terms here
> 
> Or, if you want to search several sites, set up a link or bookmark 
> something like this:
> 
> https://www.google.com/search?q=searchKey+site:lilypond.org/doc/v2.19+
OR+site:lsr.di.unimi.it/LSR+OR+site:lilypond.1069038.n5.nabble.com
>
> 
> 
> 
> Knute Snortum (via Gmail)
> 
> On Fri, Mar 18, 2016 at 12:02 PM, Jaime Oliver
> <address@hidden <mailto:address@hidden>> wrote:
> 
> well, some examples of the LSR <http://lsr.di.unimi.it/LSR/Browse>
> have "2.18 or higher” so you’d technically miss those if you only
> search for 2.19 examples. I guess there are also a certain number
> of core features that remain compatible through all versions, so
> there is a fair chance that these might work even if the version
> says 2.16.
> 
> best,
> 
> J
> 
> 
> 
>> On Mar 18, 2016, at 2:57 PM, Kristin Rollins 
>> <address@hidden <mailto:address@hidden>> wrote:
>> 
>> Searching with Google tends to be more effective for me in
>> solving my issues with learning LilyPond and troubleshooting my
>> work, especially with the ability to simply type the query into
>> the address bar of my browser. (Though that is after I took the
>> time to go through the learning manual and at least review what
>> documentation is available to become familiar with it.)
>> 
>> The one thing I have learned, after a couple of instances of 
>> finding the wrong version's documentation (or multiple versions
>> of the documentation): I always start my search with:
>> 
>> lilypond 2.19
>> 
>> and then my search terms. That will usually make the official 
>> documentation for the proper version come to the top of the
>> search results and lower the risk of finding answers that relate
>> to previous versions.
>> 
>> Kristin
>> 
>> -- Kristin Rollins address@hidden
>> <mailto:address@hidden> Portsmouth, VA
>> 
>> On Fri, Mar 18, 2016, at 06:44 AM, David Kastrup wrote:
>>> That's one reason why it makes sense to look at the
>>> accompanying documentation of a LilyPond installation rather
>>> than search blindly for something on the net (which will
>>> frequently deliver outdated information and infrequently
>>> advance information).
>> 
>> _______________________________________________ lilypond-user
>> mailing list address@hidden
>> <mailto:address@hidden> 
>> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> _______________________________________________ lilypond-user
> mailing list address@hidden <mailto:address@hidden> 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
> 
> 
> 
> _______________________________________________ lilypond-user
> mailing list address@hidden 
> https://lists.gnu.org/mailman/listinfo/lilypond-user
> 
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v2.0.22 (GNU/Linux)

iQIcBAEBAgAGBQJW+vZFAAoJEAF3yXsqtyBlpCgP/iXycSX7BWNmju9cOXC22BKL
Ybu4WWOUzqceeXCyi4xg1mkZWtiT3CwXzZrGxoB54JeSrZqQXE+7u5iCNeQmxC45
8MS2RrRLwzz+XrM3W1/x5N6UCIGErU/uk7kFk1bkasY0krOQSe2wIFcME4x727oF
/g1Ytqk9vC2Y3FvOvEccLSi1DxAdr3qy190DcOnqv2KINYiKywpgwxfWdrGys+oy
NIvUlweKBbFESHEmcrf04dSLViqj9dT0xnLX4K35y2ovoFQdSoteQ7hK7gmyWhrR
mp85z1w+lJPSzuUA5s9guur0vRL/9dUZ1ldDeneggrfQIMqG84WXEbg4oZRkIyGL
VTOL6QwELNS3+8lOa64DQHCwh2KJBv5C6cau4g7ur//hQ1xrsUz3gsILx/819lEz
8rrM4tzQuKehxpt5KkfmWU7pzgawF1E6k6hlAD5sC6VpM+ysXUi2RYaXyW8xgbDc
9s7n08oOhGzD8/ibczJjGXpZkPMfOk+W3NSYIcsn2GRC03/qSL2xGUt+NP6W0+t5
lqwfEVx2szIRLfKJDDgjex1mmvUt1sgaYAR1/NJI6pztzGp/MPSOW+HvrOLQpknC
wqbP66WZhCdnCj9ufOpZfIbyghaV6ju62sXHl9aROKpV3IVxWAO3RIgjiS8PsDQR
2AHcJoNllXmj+ZZ2oei/
=XJRY
-----END PGP SIGNATURE-----