From: Joe R. J. <jj...@cl...> - 2002-01-15 23:57:08
|
On Tue, 15 Jan 2002, Gilles Detillieux wrote: > Date: Tue, 15 Jan 2002 17:05:37 -0600 (CST) > From: Gilles Detillieux <gr...@sc...> > To: Geoff Hutchison <ghu...@ws...> > Cc: htd...@li... > Subject: Re: [htdig-dev] Re: Progress towards 3.1.6 > > According to Geoff Hutchison: > > On Tue, 15 Jan 2002, Gilles Detillieux wrote: > > > 1. better configure test for regex problems on BSDi > > > > I don't know if this will ever become "automatic," but it looks like we > > can relatively easily have a --with-rx flag to the configure script which > > will bypass the included regex code (and use the rx code instead). > > > > Does this seem like a reasonable workaround? > > That's reasonable to me. But back in October, you had suggested an > automatic test for the machine triplet "*-*-bsdi*". Have you given up on > that idea? It seems it's only been BSDI systems that have had problems > with the bundled GNU regex code. I think manual overrides with --with-... > options are a good idea, but an automatic test for setting the default > would be handy and may cut down the number of questions on the list. I believe --with-rx is the better solution. Administrators of systems that have not manifested any problem with the bundled GNU regex code, would have an option to compare htdig performance with and without it. I am not sure if the automatic test for the machine triplet "*-*-bsdi*" would work; however, I wouldn't mind to have both solutions;^) Regards, Joe -- _/ _/_/_/ _/ ____________ __o _/ _/ _/ _/ ______________ _-\<,_ _/ _/ _/_/_/ _/ _/ ......(_)/ (_) _/_/ oe _/ _/. _/_/ ah jj...@cl... > > > 2. way to override "no server" problem > > > > I'm not quite sure what you mean by this. > > Since 3.1.5, if htdig fails to connect to a server, it sets the "dead > server" flag and won't try again to contact that server, giving instead a > bunch of "no server" errors. In most cases, that's the best thing to do, > but a number of users expressed a preference for the old way, or something > more fail-safe like waiting a while and trying that server again later. > > > > 4. a "match all documents" mechanism in htsearch > > > > This IMHO, is no small feat unless you hack htsearch to totally bypass the > > parser and htfuzzy phases for some specific query. (As in, if the query is > > just '*' and nothing else, it will return all documents and then > > restrict, exclude, etc. But something like 'foo and * not bar" is subject > > to the normal parsing.) > > > > Again, if this seems like a reasonable workaround, I can write this. > > It's certainly reasonable for the purpose in mind (the what's new facility). > Thanks! > > -- > Gilles R. Detillieux E-mail: <gr...@sc...> > Spinal Cord Research Centre WWW: http://www.scrc.umanitoba.ca/~grdetil > Dept. Physiology, U. of Manitoba Phone: (204)789-3766 > Winnipeg, MB R3E 3J7 (Canada) Fax: (204)789-3930 > > _______________________________________________ > htdig-dev mailing list > htd...@li... > https://lists.sourceforge.net/lists/listinfo/htdig-dev |