Quantcast
Channel: sshnet Issue Tracker Rss Feed
Viewing all articles
Browse latest Browse all 1026

Commented Unassigned: Backspace in ssh stream output [2570]

$
0
0
Hi, I have no issues when using SshCommand.Execute(). However, when I create a ShellStream and attach to a StreamReader object, when I submit commands I tend to get garbled output like so:

perl -e "use LWP::Simple; my @info = head(\"https://files.example.\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\b\bfo = head(\"https://

..... snip

That is, the stream output is littered with backspaces, and the number of backspaces sometimes but don't necessarily match the number of corrections I'd expect. On the same output later, there is a case where I see X backspace characters and there truly are X "corrected" characters.

Example above: that's 64 backspace characters, but you can see that it only seems to back up 32 characters before starting from ... "fo = head" again.

Anyone have an idea about either of these?

1. Why is it doing this "correcting" at all?
2. Why don't the number of backspaces match the number of corrected characters?

Thanks much for insight anyone can provide.

P.S. I find that increasing the number of "columns" when I invoke CreateShellStream() takes care of this. I've increased from 80 columns to 1000, or even 10000, and I don't see backspaces. Anyone have thoughts about an appropriate value? Risk associated with large number of "columns"?
Comments: ** Comment from web user: drieseng **

Can you reproduce this issue consistently ?
If so, can you send me a minimal repro (both client code and server script) ?

Thanks!


Viewing all articles
Browse latest Browse all 1026

Trending Articles



<script src="https://jsc.adskeeper.com/r/s/rssing.com.1596347.js" async> </script>