- 08 3月, 2017 4 次提交
-
-
由 Marc Tiehuis 提交于
-
由 tiehuis 提交于
The --max-filesize option allows filtering files which are larger than the specified limit. This is potentially useful if one is attempting to search a number of large files without common file-types/suffixes. See #369.
-
由 tiehuis 提交于
A maximum filesize can be specified as an argument to a `WalkBuilder`. If a file exceeds the specified size it will be ignored as part of the resulting file/directory set. The filesize limit never applies to directories.
-
由 Marc Tiehuis 提交于
Fixes #391.
-
- 01 3月, 2017 1 次提交
-
-
由 David Salter 提交于
-
- 26 2月, 2017 2 次提交
-
-
由 Andrew Gallant 提交于
Fixes #383
-
由 Igor Gnatenko 提交于
-
- 24 2月, 2017 2 次提交
-
-
由 Andrew Gallant 提交于
-
由 deepy 提交于
-
- 20 2月, 2017 2 次提交
-
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
-
- 19 2月, 2017 7 次提交
-
-
由 Andrew Gallant 提交于
This commit fixes two issues. The first issue is that if a file contained many NUL bytes without any LF bytes, then the InputBuffer would read the entire file into memory. This is not typically a problem, but if you run rg on /proc, then bad things can happen when reading virtual memory mapping files. Arguably, such files should be ignored, but we should also try to avoid exhausting memory too. We fix this by pushing the `-a/--text` flag option down into InputBuffer, so that it knows to stop immediately if it finds a NUL byte. The other issue this fixes is that binary detection is now applied to every buffer instead of just the first one. This helps avoid detecting too many files as plain text if the first parts of a binary file happen to contain no NUL bytes. This issue still persists somewhat in the memory map searcher, since we probably don't want to search the entire file upfront for NUL bytes before actually performing our search. Instead, we search the first 10KB for now. Fixes #52, Fixes #311
-
由 Andrew Gallant 提交于
When the --files flag is given, ripgrep would still try to parse some of the positional arguments as regexes. Don't do that. Fixes #326
-
由 Andrew Gallant 提交于
@kbknapp <3 Fixes #327
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
All Windows specific code has been (mostly) pushed out of ripgrep and into its constituent libraries.
-
由 Stu Hood 提交于
-
- 13 2月, 2017 1 次提交
-
-
由 Andrew Gallant 提交于
-
- 10 2月, 2017 2 次提交
-
-
由 Peter Williams 提交于
This is essentially a rename of the existing `Stdout` type to `StandardStream` and a change of its constructor from a single `new()` function to have two `stdout()` and `stderr()` functions. Under the hood, we add add internal IoStandardStream{,Lock} enums that allow us to abstract between Stdout and Stderr conveniently. The rest of the needed changes then fall out fairly naturally. Fixes #324. [breaking-change]
-
由 Ahmed El Gabri 提交于
-
- 31 1月, 2017 2 次提交
-
-
由 Samuel Colvin 提交于
-
由 Daniel Hahler 提交于
The documentation says: > If `$XDG_CONFIG_HOME` is not set or is empty, then > `$HOME/.config/git/ignore` is used instead. This is the expected behavior, but the code looked at ~/git/ignore instead.
-
- 24 1月, 2017 1 次提交
-
-
由 Alexander Altman 提交于
-
- 22 1月, 2017 1 次提交
-
-
由 Andrew Gallant 提交于
-
- 21 1月, 2017 1 次提交
-
-
由 Jake Goulding 提交于
-
- 19 1月, 2017 3 次提交
-
-
由 David Stangl 提交于
-
由 Tareq A Khandaker 提交于
-
由 robi-wan 提交于
.eex is the default file ending for templates using Elixir's template engine EEx.
-
- 18 1月, 2017 3 次提交
-
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
It was missing a change about colors/styles. Fixes #330
-
- 17 1月, 2017 1 次提交
-
-
由 Peter Williams 提交于
-
- 16 1月, 2017 1 次提交
-
-
由 Andrew Gallant 提交于
This removes all use of explicit unsafe in ripgrep proper except for one: accessing the contents of a memory map. (Which may never go away.)
-
- 14 1月, 2017 6 次提交
-
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
-
由 Andrew Gallant 提交于
Currently, Rust's standard library will yield an error if one tries to write invalid UTF-8 to a Windows console. This is problematic for ripgrep when it tries to print matched lines that contain invalid UTF-8. We work around this by modifying the `termcolor` library to lossily decode UTF-8 before sending it to `std::io::Stdout`. This may result in some Unicode replacement chars being shown in the output, but this is strictly better than erroring or not showing anything at all. Fixes #318.
-
由 Andrew Gallant 提交于
-