Re: Fixing a bug on Tramp

[Michael Albinus <michael.albinus@gmx.de>]

[Please keep Cc, for the archives]

Justin Joseph Kaipada <justinjoseph0007@gmail.com> writes:

Hi Justin,

> What are we expecting here, everything looks fine until 
>
> # stty -inlcr -onlcr -echo kill '^U' erase '^H'
>
> after which new commands are not making newlines anymore, mat be
> that's what the above command is doing. then everything works fines as
> usual.

Yes, we need some massage of macOS newline handling. How are carriage
return / linefeed handled on the remote OS/390? Just CR, or LF, or
CR/LF? On <https://en.wikipedia.org/wiki/Newline>, something different
is reported, NL (?\025).

> what's the point of getting the locale -a information anyways ?.

That's a trace command, which is sent because we have tramp-verbose set
to 10. In normal operation, Tramp wouldn't send this command.

> and once again # echo \"`getconf PATH 2>/dev/null`\" 2>/dev/null; echo
> tramp_exit_status $? returns "/bin" with quotes

Yes, in your shell. Inside Tramp, the apostrophes are missing :-(

Perhaps we need some more tty settings, don't know. What happens, if you
comment the stty command inside tramp-sh.el, so it isn't sent to the
remote? Does it make a difference? Note, that the first command with the
echo \"`uname -sr`\"  sequence has worked successfully.

(Well, it would help if I could run tests towards a remote OS/390
machine myself. But I suspect this isn't possible.)

Best regards, Michael.