Sven Taute

Early versions only respected a `.sift.conf` in the current working directory, but since version 0.3.3 sift searches the parent directories for a `.sift.conf` file and uses that. So it should...

I agree that something like `.siftignore` would be much more practical and flexible in such cases. I will implement something like it - thanks for sharing your thoughts on this!

@ggreer and @BurntSushi just suggested that search tools should use the same file for custom ignore patterns - I think that is a great idea (see BurntSushi/ripgrep#40 / https://news.ycombinator.com/item?id=12568822). I...

Thanks for your suggestion. I focused on a correct support of the various possible .gitignore patterns for the initial implementation, as I think that is most important for the majority...

The `--path` option only works as a filter on the given search targets. You did not specify a search target, so sift searches in the current directory by default and...

It is difficult to solve this without some test data, but please try the following: `sift -z 'PATTERN' /www/logs --path 'mpri2(1|3|5)/http_log.*2016.02.11.*log.gz'`

You are correct about the existing networking code. A webgui option is one of the major features I am already working on - this will definitely be part of a...

Thanks for the suggestion - I am just now working on the release of version 0.6.0 that will include .gitignore support, it should be up within the next hour (I...

I just read through the specification for .hgignore files - it looks nice on the first view, but the details are quite complicated. On the other side most people seem...

As mentioned, I will release them some day - but that will still take some time as I want to clean up the scripts prior to releasing them, and currently...