From: "Laurent Malvert" <laurent.malvert@gmail.com>
To: "Fans of the OS Plan 9 from Bell Labs" <9fans@cse.psu.edu>
Subject: Re: [9fans] Newbie Questions
Date: Fri, 1 Jun 2007 20:07:35 +0200 [thread overview]
Message-ID: <a186e7650706011107s7c5ea6a0u7a8e6fa8b8020551@mail.gmail.com> (raw)
In-Reply-To: <fb4c8d190706010909n41983c10y813b6b5d9af4609c@mail.gmail.com>
On 6/1/07, Lorenzo Fernando Bivens de la Fuente <lorenzobivens@gmail.com> wrote:
> On 6/1/07, Laurent Malvert <laurent.malvert@gmail.com> wrote:
> > On 6/1/07, andrey mirtchovski <mirtchovski@gmail.com> wrote:
> > > i find google to be a very good search engine for the wiki:
> >
> > sure, except that you cannot be sure that google indexed all the pages
> > you want, whereas with your own engine you can control that
> > completely.
> >
> > But yes, Google serves its purpose well and I use it for local site
> > searching once in a while... when I don't find what I want with the
> > site's own search feature.
> > It's a great 'general' tool, as a safeguard.
> >
>
> And as far as I know, it can be embedded on any website...
And ? I don't see the relation ?
Yes we could add the embedded google searchbar, it would still use the
same google site: feature.
I am talking about the way the pages are being indexed.
You can tell the google robot to skip some pages (like kris maglione
suggests for the diffs) or to not index files contained in a given
folder, for instance.
But you cannot do the opposite: force it to index specific pages of a website.
That's the point I was talking about: your own embedded search engine
indexes what you tell him to.
--
Laurent Malvert [laurent.malvert@gmail.com]
{EPITECH.} - EuroPean Institute of TECHnology
next prev parent reply other threads:[~2007-06-01 18:07 UTC|newest]
Thread overview: 40+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-06-01 8:44 chutsu
2007-06-01 9:06 ` Gabriel Diaz
2007-06-01 11:17 ` erik quanstrom
2007-06-01 15:25 ` Lorenzo Fernando Bivens de la Fuente
2007-06-01 15:33 ` Laurent Malvert
2007-06-01 15:39 ` Lorenzo Fernando Bivens de la Fuente
2007-06-01 15:46 ` andrey mirtchovski
2007-06-01 16:06 ` Laurent Malvert
2007-06-01 16:09 ` Lorenzo Fernando Bivens de la Fuente
2007-06-01 18:07 ` Laurent Malvert [this message]
2007-06-04 9:08 ` [9fans] " chutsu
2007-06-04 9:33 ` W B Hacker
2007-06-01 17:23 ` [9fans] " Kris Maglione
-- strict thread matches above, loose matches on Subject: below --
2013-09-18 1:14 [9fans] Newbie questions Terry Wendt
2013-09-18 5:42 ` Deepak Chawla
2013-09-18 8:02 ` Richard Miller
2013-09-18 8:23 ` Jens Staal
2013-09-18 12:41 ` erik quanstrom
2013-09-19 14:02 ` Matthew Veety
2007-12-07 9:58 Bob
2007-12-07 12:17 ` Steve Simon
2007-12-07 14:33 ` C H Forsyth
2007-06-01 8:44 [9fans] Newbie Questions chutsu
2007-06-01 10:40 ` cej
2001-02-08 22:21 [9fans] Newbie questions forsyth
2001-02-09 9:40 ` Michael Collins
2001-02-09 15:36 ` Douglas A. Gwyn
2001-02-08 19:29 anothy
2001-02-07 21:05 Russ Cox
2001-02-08 9:42 ` Michael Collins
2001-02-07 19:05 Russ Cox
2001-02-07 18:13 ` mike
2001-02-08 9:42 ` Michael Collins
2001-02-07 18:12 nigel
2001-02-07 17:21 Russ Cox
2001-02-07 17:04 Russ Cox
2001-02-07 17:53 ` mike
2001-02-07 10:08 nigel
2001-02-07 9:46 Michael Collins
2001-02-07 17:13 ` Lucio De Re
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=a186e7650706011107s7c5ea6a0u7a8e6fa8b8020551@mail.gmail.com \
--to=laurent.malvert@gmail.com \
--cc=9fans@cse.psu.edu \
/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 NNTP newsgroup(s).