From: Jan Kybic <kybic@fel.cvut.cz>
To: Radu Grigore <radugrigore@gmail.com>
Cc: caml-list <caml-list@inria.fr>
Subject: Re: [Caml-list] ANN: cfind 0.0.0
Date: 15 Apr 2005 12:35:43 +0200 [thread overview]
Message-ID: <m2wtr4e39c.fsf@fel.cvut.cz> (raw)
In-Reply-To: <7f8e92aa0504150033198cd1b1@mail.gmail.com>
> Description: cfind is a UNIX tool that provides functionality similar
> to that of Google Desktop from the command line. It is written
> entirely in OCaml.
>
> Homepage: http://cfind.sourceforge.net/
>
> I'll appreciate any input from the OCaml community.
It looks definitely very useful. Proposed extensions and changes:
- configurable choise of a lexer. For example there could be a table
(read from a configuration file) with regular expressions matching
path and file names, association them to parsers.
- If I understand your code correctly, in TeX files only
command names are indexed, is it correct? Then I might prefer a
different lexer, which ignores comments and command names and
indexes the words in the text.
- It should be also possible to apply other configurable filters to
the files before indexing. An example would be to decompress
all "*.gz" or "*.bz2" files before indexing
- More complicate logical expressions defining match, in the spirit of:
"functional" AND "lazy" AND NOT "Haskell"
- It would be nice to be able to break files into smaller units and to
find the units which match, not the whole file. A typical example
would be email in mbox format, or perhaps functions in a program.
Good luck,
Jan
--
-------------------------------------------------------------------------
Jan Kybic <kybic@fel.cvut.cz> tel. +420 2 2435 5721
http://cmp.felk.cvut.cz/~kybic ICQ 200569450
prev parent reply other threads:[~2005-04-15 10:35 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-04-15 7:33 Radu Grigore
2005-04-15 10:35 ` Jan Kybic [this message]
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=m2wtr4e39c.fsf@fel.cvut.cz \
--to=kybic@fel.cvut.cz \
--cc=caml-list@inria.fr \
--cc=radugrigore@gmail.com \
/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).