quiet mode (-q) should suppress "no matches" error
Bug #381282 reported by
Karl Fogel
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
bzr search plugin |
Incomplete
|
Undecided
|
Unassigned |
Bug Description
Currently bzr-search treats no matches as an error, even when -q is given:
$ bzr search -q string-
bzr: ERROR: No matches were found for the search [u'string-
$
Getting no hits is a very common occurence. I'm not sure it should be an error
even by default; IMHO it definitely shouldn't print an error when -q is passed.
Yes, this would be easy to patch, and if I get a chance I will. I just wanted to
file the bug before I forgot.
summary: |
- quiet mode (-q) should suppress the "no matches" error message + quiet mode (-q) should suppress "no matches" error |
To post a comment you must log in.
I'm not sure I agree here. Should bzr search -q foo not output its requested results?
-q to me isn't 'have no ui' its, 'show no chatter'. A complete lack of results isn't chatter, its the result.