Doug Warren

Reported issues: 1

06:51 PM SupoSE Bug #306: Use of Lucene StandardAnaylzer treats _ as word delimter: Sorry to follow myself up but I forgot to mention how scan is done: There's a daily script run that basically goes as: svn update /home/thebigwavenet/supose-0.6.2RC1-447/bin/supose scan --url file:///home/svn/tsunami-repo --index /home/thebigwa...
06:40 PM SupoSE Bug #306: Use of Lucene StandardAnaylzer treats _ as word delimter: Karl Heinz Marbaise wrote: > Hi Doug, > > Sorry I thought I was on notification for bugs, but didn't get an E-Mail. > No problem. > > > If you wish I can compress and throw on-line example repositories and output as to how I'm calling it t...

02:44 AM SupoSE Bug #306: Use of Lucene StandardAnaylzer treats _ as word delimter: Sorry I thought I was on notification for bugs, but didn't get an E-Mail. If you wish I can compress and throw on-line example repositories and output as to how I'm calling it that demonstrate the issue.

09:52 PM SupoSE Open Discussion: RE: Supose and HEAD: Karl Heinz Marbaise wrote: > Sorry took a little time... > > at the momment SupoSE does not directly support this...but what you can do is to limit the search on a [[SearchingRevisions|particular revision or a range of revisions ]] for example...

07:31 PM SupoSE Open Discussion: Supose and HEAD: Is it possible to limit Supose searches to either files that exist in the HEAD revision or even better yet files *AS* they exist in the HEAD revision? If I refactor something and want to search to see where it's still being used I'm getting all o...
07:29 PM SupoSE Bug #306: Use of Lucene StandardAnaylzer treats _ as word delimter: I am indexing a .c file with a codebase that uses _ to form functions, in the 'StandardAnaylzer' of Lucene, _ is considered a white space character. As such a search for say: 'Is_variable_on' would become 'is variable on' this combined with a mi...

Also available in: Atom