This makes sense to me.
I think there is no sane way to handle UTF-8 characters of width != 1...
On Thu, Apr 12, 2012 at 05:44:19AM -0700, Matthew Dempsky wrote:
> While reading the mosh research paper[1], I noticed we don't have
> IUTF8, which is necessary for backspace to work correctly in can
Matthew Dempsky wrote:
> While reading the mosh research paper[1], I noticed we don't have
> IUTF8, which is necessary for backspace to work correctly in canonical
> mode (ICANON) with UTF-8 characters.
In principle, IUTF8 should also be added to ssh(1).
I see that the Debian people already mad
Matthew Dempsky wrote:
> While reading the mosh research paper[1], I noticed we don't have
> IUTF8, which is necessary for backspace to work correctly in canonical
> mode (ICANON) with UTF-8 characters.
Here's a quick diff for stty(1).
Index: modes.c
While reading the mosh research paper[1], I noticed we don't have
IUTF8, which is necessary for backspace to work correctly in canonical
mode (ICANON) with UTF-8 characters.
[1] http://mosh.mit.edu/mosh-paper-draft.pdf
I took a quick stab at implementing it, and it didn't seem too bad.
See kernel
