After my attempt to search for "nsIForm>" in LXR today gave
me a nice useless error message because I had the temerity to not want all
those instances of nsIFormContro we have in our source, I started
seriously thinking about alternatives to lxr.mozilla.org. I
wonder how hard it would be to set up glimpse locally to index one of my
trees.... Has anyone tried this yet?
LXR (the upstream version) even has the ability to use glimpse, although they recommend using something else instead (can't remember off hand)
Its a real pain to set up, though...
Posted by: bbaetz on November 17, 2005 1:49 AMSearch for nsIForm%3E
Posted by: Anonymous on November 17, 2005 3:39 AMYou could just set up LXR locally.
Posted by: christian biesinger on November 17, 2005 6:08 AMWhat would be really cool is if people worked more on LXR. I'm trying to get it running so I can spew out patches, but I have a very limited amount of both time and ability. If anyone is around who has crazy Perl knowledge and lots of free time, there are plenty of bugs waiting to be fixed 'round those parts.
Posted by: Jweb_Guru on November 17, 2005 8:06 AMnsIForm%3E works! Too bad that I don't remember all the hex codes off the top of my head. And I find it _really_ odd that double-escaping basically works here. That suggests to me that someone is unescaping prematurely.
biesi, I'd really rather not run an HTTP server, for security reasons.
Jweb_Guru, the problem is that this _used_ to work. It got broken by a "security fix" when the last LXR upgrade happened.
Posted by: Boris on November 17, 2005 9:09 AMLXR should also work with Swish-e which seemed better based on the documentation, but I have no actual experience using it (yet).
Posted by: Heikki Toivonen on November 17, 2005 2:04 PMYou should be able to install Beagle and get it to index your local trees. I should try this since Beagle is actually preinstalled in SUSE10...
Posted by: Robert O'Callahan on November 17, 2005 3:13 PM