Dan Fandrich

I don't think that example program will set the TERM variable on the remote shell. Try setting that manually before running vim.

You can test this theory without any code. Just log in to the server by ssh and type "export TERM=whatever" and replace "whatever" with the proper terminal type (probably xterm)....

I think we already support one build system too many.

WRT the WinCNG test, you're probably hitting https://github.com/libssh2/libssh2/issues/804 which would not be an issue with this PR.

I encountered at least one failing WinCNG build on almost every CI run over the past month. If you restart the failing jobs on Appveyor, it usually runs fine the...

The traces should end up in the console output. See for example this run: https://ci.appveyor.com/project/libssh2org/libssh2/builds/46289843/job/5sww8cvj4oyky70t

Could it be that the particular build you're looking at is not built in debug mode so the internal trace debug logging is compiled away?

That would be great, but it shouldn't halt submission of this PR. You might want to rebase the PR and create read_tests for the new ETM modes by just copying...

On Thu, Mar 09, 2023 at 04:31:26AM -0800, Anders Borum wrote: > I still have CI errors and this time not just for Windows builds. It is almost > always...

What command-line are you running that gives you this error?