it's a bug that the ellipsis is printed when unicode is false (be it autodetected from TERM and the locale, or be it via --unicode=never); in the same way we change the tick to an asterisk, we should have a fallback for the ellipsis in the channel.
It's an oversight; I'll fix it.
A lot of text from snapd is going to be in utf8 however, and this won't catch everything. For example, if in a non-utf8 locale, "snap info unifonter" is going to look interesting.
it's a bug that the ellipsis is printed when unicode is false (be it autodetected from TERM and the locale, or be it via --unicode=never); in the same way we change the tick to an asterisk, we should have a fallback for the ellipsis in the channel.
It's an oversight; I'll fix it.
A lot of text from snapd is going to be in utf8 however, and this won't catch everything. For example, if in a non-utf8 locale, "snap info unifonter" is going to look interesting.