[Bug 2478] Escape sequences (starting with ~) don't work when remote shell is BusyBox ash

[bugzilla-daemon at bugzilla.mindrot.org]

https://bugzilla.mindrot.org/show_bug.cgi?id=2478

--- Comment #3 from Alex Dowad <alexinbeijing at gmail.com> ---
dtucker: Thanks for pointing that out. I realized the same when falling
asleep yesterday. Will post an updated patch.

djm: "I'm not sure the pushing back of escape sequences to the bin
buffer is correct" -- this is exactly what happens to them in the
existing code, without this patch. That aspect is unchanged. The only
thing which changes, is that <CR><escape><escaped char> sequences are
processed by the client *even if* an ANSI escape appears in between the
<CR> and <escape> or between the <escape> and <escaped char>.

There's no reason why OpenSSH should intercept and change or remove
ANSI escape sequences. That would make a remote shell behave
differently from a local shell. By writing them into 'bin', just as
they appear in the input, SSH can be 'transparent' as far as the
interaction between terminal emulator and remote shell goes.

-- 
You are receiving this mail because:
You are watching the assignee of the bug.
You are watching someone on the CC list of the bug.