[mosh-devel] stripping locale support from mosh

[Keith Winstein]

Hi Ed,

You can force mosh to start up outside a UTF-8 charset by editing the
is_utf8_locale() function (in src/util/locale_utils.cc) to always
return true. (Patch attached.)

As you can appreciate, it's a lot easier to maintain a terminal
emulator for _one_ charset than to try to make it agile and support
more than one. (UTF-8 vt220s are not backwards-compatible with 8-bit
vt220s, unfortunately, and screen historically has had loads of bugs
trying to convert between the two.) I don't think we're really eager
to support Mosh in more configurations because it gets complicated
quickly.

But you're welcome to turn off our paranoid checks if you need to in
your configuration. Hope this helps.

Best regards,
Keith

On Fri, Oct 5, 2012 at 4:09 AM, Edward Peschko <horos11 at gmail.com> wrote:
> All,
>
> Again, this is in pursuit of better, more bullet proof connections in
> automation. Could mosh perhaps be able to disable locale support, or
> make it optional?
>
> For several applications of mosh (including mine) unfortunately this
> is critical - the 'devices' we produce, for example are stripped down
> versions of centos and hence DON'T have any locale info installed (in
> fact there isn't even the locale binary) and hence the locale
> requirement makes using mosh infeasible..
>
> Having an option to compile mosh with plain-old ascii would be great
> here - elsewise I'm not sure how I could use mosh as I envision here.
>
> Thanks much, and workarounds again are appreciated..
>
> Ed
> _______________________________________________
> mosh-devel mailing list
> mosh-devel at mit.edu
> http://mailman.mit.edu/mailman/listinfo/mosh-devel
-------------- next part --------------
A non-text attachment was scrubbed...
Name: mosh-ascii.patch
Type: application/octet-stream
Size: 436 bytes
Desc: not available
Url : http://mailman.mit.edu/pipermail/mosh-devel/attachments/20121005/27ffa1e0/attachment.obj