os/doc
3
0
Fork 0
Code Issues Pull requests Projects Releases Wiki Activity

Web pages, may I introduce you to CVS. CVS, these are the web pages.

Browse source 
Yes, this is supposed to be a new top level in the repository.

For the moment any changes to this area must be cleared by myself
or Jordan.  Once the kinks are worked out, the policy will probably
be relaxed.
This commit is contained in:
John Fieber 1996-09-24 17:46:04 +00:00
commit 38df6f51c6
Notes: svn2git 2020-12-08 03:00:23 +00:00 
svn path=/www/; revision=543
189 changed files with 30753 additions and 0 deletions
Download patch file Download diff file Expand all files Collapse all files

50
data/searchhints.sgml Normal file
View file

@ -0,0 +1,50 @@
<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 3.2//EN" [
<!ENTITY date "$Date: 1996-09-24 17:45:44 $">
<!ENTITY title "Searching Hints">
<!ENTITY % includes SYSTEM "includes.sgml"> %includes;
]>
<html>
&header;
<h2>If you got lots of irrelevant results...</h2>
<ol>
<li>If you search for several words such as "<tt>quantum
hard drives</tt>", an OR is implied meaning that to be
counted as relevant, only one of the word has to appear
in a message. To find only messages with all three
words, change the search to "<tt>quantum and hard and
drives</tt>"<p></p></li>
<li>If you still get lots of irrelevant messages, see if
they have something in common. If so, you can exclude
them with the <tt>not</tt> operator. For example
"<tt>quantum and hard and drives not ide</tt>" will
exclude any messages about ide quantum hard drives.</li>
</ol>
<h2>If you don't think you got everything you should have...</h2>
<ol>
<li>If one of your keywords has variant forms, be sure to
enter all relevant forms. If you are searching for
"<tt>buslogic</tt>", you might change it to "<tt>buslogic
or bustek</tt>".<p></p></li>
<li>Words with varying suffixes can be wildcarded.
Searching for "<tt>drive*</tt>" will pick up words such
as <tt>drive</tt>, <tt>drives</tt>, <tt>driver</tt>,
<tt>drivers</tt> and so on.<p></p></li>
<li>Try discarding words that could be implied by the
context of the message. For example "<tt>quantum and
hard and drive</tt>" might miss some relevant messages
that "<tt>quantum and drive</tt>" would get.</li>
</ol>
<hr>
<a href="search.html">Return to the search page</a>
&footer;
</body>
</html>