Say you momentarily forget that boring needs to contain regexes, not
globs, and your boring file contains just:
*.whatever
Then executing `darcs wh -l` gives:
darcs failed: Text.Regex.Posix.String died: (ReturnCode 13,"Invalid
preceding regular expression")
Can we make this slightly more user-friendly? The error is fairly
descriptive, but doesn't necessarily explain why and where it's come from.
N.B, you must be in a non-empty repo for the error to occur (touching a
single file, in a clean repo is enough), as a guess, I'd say this is due
to the regex only being used (and thus created) if there is a non-empty
tree to be searched.
The following patch sent by Owen Stephens <darcs@owenstephens.co.uk> updated issue issue2065 with
status=has-patch
* resolve issue2065: filter and give warning for any malformed boring regexs.
Ignore-this: cdfa5b72c74f87bc362463b4207adc63
The following patch sent by Owen Stephens <darcs@owenstephens.co.uk> updated issue issue2065 with
status=resolved;resolvedin=2.10.0 HEAD
* resolve issue2065: filter and give warning for any malformed boring regexs.
Ignore-this: cdfa5b72c74f87bc362463b4207adc63