junkblocker / codesearch Goto Github PK

From @suntong on January 18, 2017 19:18

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.

Copied from original issue: junkblocker/codesearch-pre-github#12

Look into for releasing binaries.

From @DXist on December 4, 2014 9:22

Thank you sharing your fork!

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

Copied from original issue: junkblocker/codesearch-pre-github#6

Would it be possible to allow searches across multiple lines in a file?

From @TheCycoONE on January 28, 2016 14:44

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

Copied from original issue: junkblocker/codesearch-pre-github#9

First, I'd like to thank you for the work you have put into expanding codesearch.

One question, though: What's the reason for skipping the entire file if a long line is encountered, instead of just ignoring the line?

Would it be possible to parallelise the indexing process, or at least parts of it, to improve the overall speed?

Running this over a 6.4GB repository with 275,000 files in it, on Windows, the process is neither bottlenecked on CPU or disk IO, but the process takes over an hour. Running two index commands on two repos on the same NVMe SSD, in parallel, results in a disk IO of around 20% and barely taxes one core. The memory usage is only around 400MB per process.

I suspect that sequentially opening each file, reading and processing contents, storing the results, then moving onto the next file is causing heavy throughput limitations when there are many thousands of small files.

I don't know enough Go to implement this myself, unfortunately. Is this something you could potentially investigate?

From @cloudspeech on October 29, 2015 14:10

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 > ?

Copied from original issue: junkblocker/codesearch-pre-github#8

I think that would be a great feature.

Often you need to search through a lot of files to find out why some obsolete code doesn't working. Now you have to run shell scripts just to get file list for indexing.

Hi,
The Windows version of codesearch is broken because it doesn't properly close any of its file handles before it tries to remove the files.

My fork has this change which fixes this. My fork has diverged (I added a tempDir argument so that I could move the temp files where I wanted them), but someone should be able to port over my changes without too much issue.

Installing codesearch (my codesearch) (github.com/junkblocker/codesearch/cmd/...)
go: found github.com/junkblocker/codesearch/cmd/... in github.com/junkblocker/codesearch v1.1.0
go: finding module for package github.com/google/codesearch/index
go: finding module for package github.com/google/codesearch/regexp
go: found github.com/google/codesearch/regexp in github.com/google/codesearch v1.2.0
SUCCESS.

Somehow google/codesearch/regexp is being considered v1.2.0 and fetched?

Does it depend on GOPROXY being used?

Hi
I can't find the pre-built binaries anywhere!