Andrew Gallant d1389db2e3 search: better errors for preprocessor commands ...

If a preprocessor command could not be started, we now show some
additional context with the error message. Previously, it showed
something like this:

  some/file: No such file or directory (os error 2)

Which is itself pretty misleading. Now it shows:

  some/file: preprocessor command could not start: '"nonexist" "some/file"': No such file or directory (os error 2)

Fixes #1302

2019-06-16 19:02:02 -04:00

..

app.rs

doc: add note about --pre-glob

2019-04-15 17:47:48 -04:00

args.rs

ripgrep: max-column-preview --> max-columns-preview

2019-04-15 06:51:51 -04:00

config.rs

style: fix deprecations

2019-06-16 18:37:51 -04:00

logger.rs

ripgrep: migrate to libripgrep

2018-08-20 07:10:19 -04:00

main.rs

style: fix deprecations

2019-06-16 18:37:51 -04:00

messages.rs

deprecated: remove use of ATOMIC_BOOL_INIT

2019-01-29 13:05:16 -05:00

path_printer.rs

ripgrep: migrate to libripgrep

2018-08-20 07:10:19 -04:00

search.rs

search: better errors for preprocessor commands

2019-06-16 19:02:02 -04:00

subject.rs

binary: rejigger ripgrep's handling of binary files

2019-04-14 19:29:27 -04:00