-
-
Notifications
You must be signed in to change notification settings - Fork 213
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Terminal output messes up and wraps at 80 characters #1416
Comments
80 is only used as fallback if there is no Looks like nvim-dap-ui sets one: https://github.com/rcarriga/nvim-dap-ui/blob/e94d98649dccb6a3884b66aabc2e07beb279e535/lua/dapui/elements/console.lua#L51 In addition to returning the buffer it would have to return the window number. That said, using |
Thanks for your answer! When I use vim.o.columns, this is what I get:
It just wraps at random locations, instead of not wrapping at all. As a side point, generally, the entire terminal output is super buggy too. When resizing the window, lines get duplicated, moved to the wrong spots, characters disappear, etc. Not sure if this happens only on my PC, please do let me know! Thank you! |
Debug adapter definition and debug configuration
Using
nvim-dap
withnvim-dap-ui
Debug adapter version
No response
Steps to Reproduce
Start a program, open nvim-dap-ui terminal, and see that terminal output is wrapped:
Expected Result
Should not wrap the terminal output. When user enables wrapping, it should wrap on the window width.
Actual Result
Terminal output wraps.
The width 80 is specified in session.lua. This width is passed to the vim pty that's started. The vim pty is what causes the problem I think, since a fixed width has to be passed, and it wraps based on that.
This is a major issue for viewing console logs. When viewing longer stack traces it's very hard to read what's going on.
Now there is a another issue as well, but I am not sure if this happens due to the wrapping or not. Here an example of the terminal output:
=================================...
Even though I print before the error happens, the characters get wrongly mixed into the error:
However, when I print the lines received from
on_stdout
in order, this is what I get:The order and the messages are correct here, but once the pty vim window is reached, the output gets messed up.
Are there any solution to these problems?
Thanks for your awesome plugins and your help!
The text was updated successfully, but these errors were encountered: