junkblocker/codesearch-pre-github

Moved to https://github.com/junkblocker/codesearch

codesearch-pre-github's Issues

Multiple code repo search

Expanding on the idea from #9, I think the best solution is to separate different code repo into different indexes, because after all, developers working on a single project is rather rare -- I personally need to do code search on many different code repos.

I propose just adding a -name to both index and search program, to separate different indexes.

Further, it's not only apply to different code repo, but even within the same repo, you can use -name to divide them into logical groups whatever you like, if you find eliminating a section is constantly needed.

How to use codesearch

Anyone care to throw a quick scribble on how to use codesearch
in https://github.com/junkblocker/codesearch/wiki?

I only know first to do the index, then to do the search, but no more details than that...

Highlight matches

Thank you sharing your fork!

It would be nice to support match highlighting. Ideally results could be highlighted both in codesearch and unite-codesearch.

Windows + any source.

Thanks for sharing your fork with us!

I really would like to use this fork for Unite codesearch.

Due to work requirements, I'm currently bounded to Windows. The Codesearch binaries for Windows are working fine (e.g. they are stored in my path, when I do csearch test, they're working fine.

It seems they're not working together with your Unite codesearch.

Is there any chance to get this compiled into a binary, in order to get your plugin working for for Windows? Thanks in advance.

Exclude path for csearch

It would be convenient to be able to define a regex exclude path (similar to csearch -f but to not match instead)

index: merge of index fails

Over on issue #50 on the google codesearch project I've been trying to sort out a problem where cindex fails to properly merge index files on windows. Someone over there said that you might be interested in addressing this problem, so here I am.

The main issue as far as I can tell is that the merge algorithm mmap's a few files but doesn't unmmap them. As a result, windows fails to overwrite the original index with the merged index (i.e. because the original index is mmap'd and, thus, apparently not writable). My diagnosis may well be incorrect in some details, but I'm pretty certain that cindex is unable to overwrite the original index.

Could you perhaps look at this and verify that I'm at least on the right track? And do you have any suggestions on how to best resolve this? I'm a newbie with go, but this feels like something that should be easy to address in the right hands.

Incremental indexing

Great to discover today there's an actively worked on fork of codesearch!

I am using codesearch already, and noticed that with lots of files reindexing is slow.

It would be great if one could tell the indexer to (re-)index a few files only and merge that efficiently into the existing index. Cursory inspection of the code tells me this should be doable.

A strong plus would be to read the file names - 1 per line - from a (named or regular) pipe, or else a regular file, and index those as soon as a new line becomes available.

Maybe an option --reindex-using < pipeOrFile > ?