From: Martin C.Atkins <martin_ml@parvat.com>
To: Fans of the OS Plan 9 from Bell Labs <9fans@cse.psu.edu>
Subject: Re: [9fans] some shell scripts
Date: Thu, 14 Oct 2004 10:59:26 +0530 [thread overview]
Message-ID: <20041014105926.08edbf1f.martin_ml@parvat.com> (raw)
In-Reply-To: <ee9e417a041013153822acb741@mail.gmail.com>
Hi,
On Wed, 13 Oct 2004 18:38:15 -0400 Russ Cox <russcox@gmail.com> wrote:
>...
> Second, inspired by reading about Nemo's tags,
> I realized that, on Unix, I use locate | grep way too much
> and I'm sick of typing really long path names.
Reading about Nemo's tags, and Russ' L, I wonder what people here think
about Beagle? (see:
http://www.gnome.org/projects/beagle/
)
I saw a demo a couple of weeks ago, and it was quite impressive.
Especially impressive was the fact that search results were updated
dynamically (within ~1/2s) when (matching) files were
created/destroyed.
This pretty-much requires a mechanism for the kernel to tell a user
process about changes to the filesystem, which sounds horrible, but
seems to work (they use inotify. Windows, apparently, has had such a
mechanism for years). Obviously, one does not want this to recurse :-(
What would be the "Plan 9 way" of achieving this? I can't see how
binding a fileserver on / (or even on my home directory) could have
reasonable performance, even if it could be made to have the right
semantics! Running a full filesystem scan every 0.1s would not be
very attractive! :-)
Note that Beagle searches more than just the filesystem, but that's
another story. All in all, Beagle-like facilities do look rather
attractive - it's sort of a super-google (i.e. uses google to search
the web. It can also search all/only the webpages that you have
visited - now that's something I really need :-)!
Martin
--
Martin C. Atkins martin@parvat.com
Parvat Infotech (Private) Limited http://www.parvat.com
next prev parent reply other threads:[~2004-10-14 5:29 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 22:38 Russ Cox
2004-10-14 5:29 ` Martin C.Atkins [this message]
2004-10-14 6:50 ` geoff
2004-10-14 9:56 ` Martin C.Atkins
2004-10-14 15:29 ` Nigel Roles
2004-10-15 0:25 ` geoff
2004-10-15 0:28 ` Russ Cox
2004-10-15 0:38 ` geoff
2004-10-14 9:22 ` Fco. J. Ballesteros
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=20041014105926.08edbf1f.martin_ml@parvat.com \
--to=martin_ml@parvat.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).