On Thu, Feb 13, 2020 at 10:55 AM Stefan Baur <[email protected]> wrote: > > I deeply doubt that the clipboard CONTENT is responsible for the > > problems. That's merely a problem in the workflow. > > Are you sure? Some reports I received (though I'm still waiting for the > final test results) hinted that special characters might be triggering > it. Things outside the 7-Bit or 7-Bit+usual-Windows-codepage range. > Things like accented characters or "unusual" whitespace (not a mere > blank, \t, \r, or \n, of course).
Well, I argue from the code side. And there the content cannot influence the workflow. But I am only talking about the clipboard code in nxagent. Maybe we face a bug in the nxcomp lib here. Or in the vcxsrv clipboard code. > > My approach is rather adding a debug facility that can be enabled at > > runtime instead of compile time so that a user can enable it as > > needed. > > > > A zapping keystroke could be implemented but I really consider as a > > temporary. I'd love to see the problems vanish altogether... > > The thing is, if you log the content of the clipboard(s) on both ends > *before* you zap, that info might help you with debugging this. > Think of it as a "clipboard coredump". Of course it does not hurt. The corresponding dumping code is already there. I think I will implement the "zap" the next days. Uli _______________________________________________ x2go-user mailing list [email protected] https://lists.x2go.org/listinfo/x2go-user
