Re: RFC: deprecate implicit-encoding "Wide character in print"behaviour

Father Chrysostomos wrote:
>I am opposed.  I write one-liners *all the time* and frequently get the
>Wide Character warnings,

For a one-liner where you want UTF-8 output encoding, you'll be
wanting the -CO option.  This actually does it correctly, without the
data dependence.  Saving you four characters of typing doesn't seem
sufficient reason to keep the broken semantics.  It's a bit... spacebar
heating <https://xkcd.com/1172/>.

>For real programs, you get an annoying warning,

But you still get the broken behaviour.

-zefram

• RFC: deprecate implicit-encoding "Wide character in print" behaviour by Zefram
• Re: RFC: deprecate implicit-encoding "Wide character in print"behaviour by Father Chrysostomos
• Re: RFC: deprecate implicit-encoding "Wide character in print"behaviour by Zefram
• Re: RFC: deprecate implicit-encoding "Wide character in print"behaviour by Kent Fredric
• Re: RFC: deprecate implicit-encoding "Wide character in print"behaviour by Zefram
• Re: RFC: deprecate implicit-encoding "Wide character in print"behaviour by Kent Fredric