[erlang-bugs] Encoding of IO devices when there is -noshell

[Dan Gudmundsson]

To not change that was intentional.

But it might have been a bad choice, I got bitten by the same thing in
escript today.

I guess this can not change in 17.1 but maybe 18.0

Opinions?

/Dan


On Thu, Apr 10, 2014 at 7:18 PM, José Valim <jose.valim@REDACTED
> wrote:

> Hello OTP team,
>
> I am using Erlang 17.0 and I have noticed that, if -noshell is given, the
> encoding for IO devices are kept as latin:
>
>     $ erl -eval 'io:format("~p", [io:getopts()]).'
>     [{expand_fun,#Fun<group.0.100149429>},
>      {echo,true},
>      {binary,false},
>      {encoding,latin1}]
>
> Setting the +fnu flag doesn't change the behaviour:
>
>     $ erl +fnu -eval 'io:format("~p", [io:getopts()]).'
>     [{expand_fun,#Fun<group.0.100149429>},
>      {echo,true},
>      {binary,false},
>      {encoding,latin1}]
>
> I am pretty sure this behaviour is present in R16, but given the new
> direction taken in 17.0, I am not sure this is an actual bug or not.
>
> I am using Mac OS X Mountain Lion but this bug was also peer verified on
> Linux.
>
> Thank you!
>
> *José Valim*
> www.plataformatec.com.br
> Skype: jv.ptec
> Founder and Lead Developer
>
> _______________________________________________
> erlang-bugs mailing list
> erlang-bugs@REDACTED
> http://erlang.org/mailman/listinfo/erlang-bugs
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://erlang.org/pipermail/erlang-bugs/attachments/20140410/1a02dc15/attachment.htm>