Package: unicode
Version: 2.9-1
Sometimes, even for the same command(!), limiting the output causes a
traceback.
Certainly using head(1), sed(1), etc. should be a legitimate use, and
not cause errors.
Here, the first try works fine.
Trying it again just for fun, causes an error.
But other times the error might be on the first time, not second, or
both, or none.
There should be no error ever.
$ unicode --max 22 -r per|sed q
U+0025 PERCENT SIGN
Too many characters to display, more than 22, use --max 0 (or other value)
option to change it
$ unicode --max 22 -r per|sed q
U+0025 PERCENT SIGN
Traceback (most recent call last):
File "/usr/bin/unicode", line 1066, in <module>
main()
File "/usr/bin/unicode", line 1063, in main
print_characters(processed_args, options.maxcount, format_string,
options.query_wikipedia, options.query_wiktionary)
File "/usr/bin/unicode", line 683, in print_characters
sys.stdout.flush()
BrokenPipeError: [Errno 32] Broken pipe
Exception ignored in: <_io.TextIOWrapper name='<stdout>' mode='w'
encoding='utf-8'>
BrokenPipeError: [Errno 32] Broken pipe
