tests/test6.err

complete: -o requires a non-empty string
complete: -l requires a non-empty string
complete: -s requires a non-empty string
make kill/pkill completions more robust (#3200) Someone running fish in an unusual locale reported that an `assert()` was firing when they typed `pkill c`. I traced it to two bugs. First, the __fish_make_completion_signals command was producing a weird result. Second, the builtin `complete` command wasn't adequately verifying its arguments. Fixes #3129 2016-07-04 20:28:21 -07:00			`complete: -o requires a non-empty string`
			`complete: -l requires a non-empty string`
			`complete: -s requires a non-empty string`