If we could just take 8-byte strings and return them, I would be happy with
that. I don't think we want to force config to be 7-bit ASCII strings. And
UTF-8 is the standard mechanism beyond that in unix-land.
On Wed, Aug 8, 2018 at 4:00 AM, Anastasia <email address hidden>
wrote:
> @John A Meinel (jameinel),
>
> That's an interesting suggestion. Would it work as you expect for
> settings that are not string though? And why utf-8? and not utf-16 or
> another format? Could we please file a separate a bug for it if we
> really think that this work should take place :)
>
> Also would it then be worthwhile considering printing all settings
> values that are strings using this new format?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https://bugs.launchpad.net/bugs/1780711
>
> Title:
> "juju config $app $item" prints multi-line strings as YAML
>
> To manage notifications about this bug go to:
> https://bugs.launchpad.net/juju/+bug/1780711/+subscriptions
>
If we could just take 8-byte strings and return them, I would be happy with
that. I don't think we want to force config to be 7-bit ASCII strings. And
UTF-8 is the standard mechanism beyond that in unix-land.
On Wed, Aug 8, 2018 at 4:00 AM, Anastasia <email address hidden>
wrote:
> @John A Meinel (jameinel), /bugs.launchpad .net/bugs/ 1780711 /bugs.launchpad .net/juju/ +bug/1780711/ +subscriptions
>
> That's an interesting suggestion. Would it work as you expect for
> settings that are not string though? And why utf-8? and not utf-16 or
> another format? Could we please file a separate a bug for it if we
> really think that this work should take place :)
>
> Also would it then be worthwhile considering printing all settings
> values that are strings using this new format?
>
> --
> You received this bug notification because you are subscribed to juju.
> Matching subscriptions: juju bugs
> https:/
>
> Title:
> "juju config $app $item" prints multi-line strings as YAML
>
> To manage notifications about this bug go to:
> https:/
>