You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Context: Wsl / ssh to remote linux and tailed some logs
When the displayed line in the terminal ends with a conventional character the copy works well.
But, if the line ends with a space character then the log line is splitted.
Check the red square on the next picture and compare with the result pasted in vscode.
As we can see with the previous log line, if the displayed line starts with a space, the complete log line is kept.
I noticed they handled it in vscode's terminal which is also using xterm.
Hello.
Context: Wsl / ssh to remote linux and tailed some logs
When the displayed line in the terminal ends with a conventional character the copy works well.
But, if the line ends with a space character then the log line is splitted.
Check the red square on the next picture and compare with the result pasted in vscode.
As we can see with the previous log line, if the displayed line starts with a space, the complete log line is kept.
I noticed they handled it in vscode's terminal which is also using xterm.
Could it be possible the simple use of their version of xterm would solve the issue?
https://github.com/Microsoft/vscode/blob/1.30.2/package.json
https://www.npmjs.com/package/vscode-xterm
In the meantime I wonder if vscode-xterm is not too far from xterm, because I did cross read this post https://codeburst.io/source-reading-how-is-new-terminal-in-vs-code-so-fast-10a40f7f8792.
Aside that, nice work! Looks promising 👍
The text was updated successfully, but these errors were encountered: