Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cindex ignores IRC log files #37

Open
GoogleCodeExporter opened this issue Mar 30, 2015 · 3 comments
Open

cindex ignores IRC log files #37

GoogleCodeExporter opened this issue Mar 30, 2015 · 3 comments

Comments

@GoogleCodeExporter
Copy link

https://code.google.com/p/codesearch/source/browse/cmd/cindex/cindex.go#132 has 
the relevant line of code. Effectively when I run cindex on my IRC log 
directory, I get an index of *only* the private conversations. Public 
conversations are in files named after the channel, so for example: 
`2014/#ubuntu.03.log`.

cindex decides to ignore dotfiles, tildefiles, and for some reason probably 
relating to EMACS, files beginning with an octothorpe ('#'). There does not 
seem to be any command-line switch to disable this file-skipping (-a would seem 
appropriate), and no way to provide custom include/exclude rules.

Since searching IRC logs is probably more common for me than searching code, it 
makes this amazing tool rather less useful for me!

Original issue reported on code.google.com by [email protected] on 27 Mar 2014 at 5:03

@GoogleCodeExporter
Copy link
Author

Just as an FYI, this is implemented in my fork at - 
https://github.com/junkblocker/codesearch .

Original comment by [email protected] on 28 Mar 2014 at 3:13

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

With thanks for your advice, please: may be you have an estimate for when your 
implementation will reach trunk.

Original comment by [email protected] on 28 Mar 2014 at 8:08

  • Added labels: ****
  • Removed labels: ****

@GoogleCodeExporter
Copy link
Author

rsc has stated in the past that this project is not super alive and is good 
enough for them in the state it is.

https://code.google.com/p/codesearch/issues/detail?id=26#c3

Also, this issue you filed has a similar bug already

https://code.google.com/p/codesearch/issues/detail?id=28

that hasn't been accepted for fixing. At this point I've kept on adding 
features  I've found useful to my code and it keeps diverging. If rsc indicates 
an interest in taking a patch, I could extract and attach one here. Otherwise 
using my fork remains your option.

Original comment by [email protected] on 28 Mar 2014 at 11:56

  • Added labels: ****
  • Removed labels: ****

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant