If I am using stdout redirection of a shell block to capture some text I am generating, errors need to go to stderr, but it would also be good if they went into the generated output. For example
for i in files*; do
if there_is_an_error; then
echo big long complicated error message goes
Hey Pádraig
On Sat, 2015-11-14 at 11:06 +, Pádraig Brady wrote:
> Unfortunately the roman numeral code points compare equal:
>
> $ printf '%s\n' Ⅱ Ⅰ | ltrace -e strcoll sort
> sort->strcoll("\342\205\241", "\342\205\240") = 0
> Ⅱ
> Ⅰ
>
> If you compare at the byte level you'll get
Oh one further solution:
- document more properly in the manpage and --help, what -u really is,
and especially that it may not behave as expected, with other
locales/collations.
Perhaps even giving an example, so that people understand the
seriousness of that.
- add companion option, maybe -U,
