Slashdot Mirror

Of course it is.

http://emacs-w3m.namazu.org/

Take that vi :P

I can't help but read "Don't text me bro" in the title of that webpage.

Imagine trying to use a CAD program, or even browse a web-forum without a mouse. The mouse still wins in some applications.

I do all my browsing with the keyboard. What's so hard to believe about that? Ironically, editing text is the hardest thing about browsing (in Firefox) which is why when I need to do a lot of editing (i.e. project wikis) I use w3m-el.

This post sponsored by Hit-a-Hint, the best thing to happen to keyboard navigation since the keyboard.

Has filters for lots of doc types, you can write more.

http://www.namazu.org/

Didn't Namazu and other full-text indexing tools handle this a long time?

I think Namazu might do (some of) the things you want. It searches plain text files, PDFs, Latex sources & DVIs, MS Office files, etc. and generates an index for fast full text searches. The index generation can of course be run in a cronjob.

The search front end can feed the results to a browser of your choice, complete with short summaries/extracts and clickable links to the documents. Its search algorithms are probably not as fancy as Google's, but I find it quite handy, mostly for indexing the PDFs of all the research articles I have downloaded over the years.

It has multiple 'filters' that allow you to index .txt .pdf .doc and various other file formats. It also has some grep like command line utilities that allows you to 'grep' for text.

Oh, and it has a perl front end for apache, and IIS. ( win32 installer available from here: www.namazu.org/windows

caveat: As with any full text search engine, the files should be reindexed on a regular basis, but this is worth it as the searches are very fast even with gigs of documents.

enjoy

How about pdumpfs?
It is plan9-like daily backup system for unix/windows.

8k wasn't much of a limit until we started storing multi-media in databases. Prior to that it was rare to hit an 8k limit. Postgresql was a little late with their support here.

Yes, multimedia and blogs seem to be the applications people are thinking of when they whinge about the 8K row limit. Hell, Slashdot was probably one of the early big users of MySQL. What these people never seem to think about is whether it's all that important, useful, or even clever to store large pieces of data (be it binary or text) in a RDBMS. Are you going to perform a query on the column storing a jpeg photo? For text (blogs, etc), I can maybe see the use of being able to simply search through the text. But IMNSHO, an RDBMS shouldn't need to also be a text search engine. Just put the damn data in a file, store the filename in the DB, and if it's text then you can use a purpose-built search engine like Glimpse or Namazu.

I recently switched to Namazu as a full-text search engine for my nmh e-mail. The combination seems to do pretty much what I want. Searches are reasonably fast and flexible, indexing is incremental, and I can script things massively.

I'd still like to get a machine-learning classifier going someday, perhaps by adapting the fine-looking dbacl, but my current combination seems like a good first cut.

http://www.namazu.org/

Namazu is a open source full-text search engine. It has various document filters (HTML, Mail/News, PDF, MS Word, Excel, Powerpoint, man page, TeX, DVI, PostScript etc...) and mharc web-based mail archiving system adopts Namazu as its search engine.

Hmmm.. Looks like an interesting concept. If you have an admin with a little time on his hands, which would probably cost you a *LOT* less than $20k, you could set up something else.

We've been using Namazu to make all of our documents searchable. It's shareware, and does a pretty decent job of it. If we make it public or private is just a matter of who you allow access. :)

I guess the days of `grep "searchstring" *` are pretty much gone.. :(

Next thing they're going to tell me is that I should start using something more modern than Pine to read my mail..

Damn straight.

w3

emacs-w3m