Results 55 comments of

I found that if I turn off stopAtEntry, the whole dap can work normally, otherwise the cursor position outside buffer will appear [someone](https://www.reddit.com/r/neovim/comments/15g22at/nvimdap_stoponentry_causes_debugger_to_crash/) have the same situation with me. ![image](https://github.com/mfussenegger/nvim-dap/assets/31800073/4d7a3f38-a47b-4869-95ed-ae3bdb3a7cef)...

i tried use newest openconsole.exe and conpty.dll, But it doesn't seem to work

> Can you try to see if you have the TMOUT env var in your distant shell? https://www.cyberciti.biz/faq/linux-tmout-shell-autologout-variable/ I tried `echo $TMOUT`, but there was no output. It should be...

This is great,i think it should be merged

i have the same problem ![image](https://github.com/neovide/neovide/assets/31800073/5a209dab-68f3-47f5-9447-e2f4a34cbaf3)

In fact, I only used win32yank, and if I didn't use win32yank, ^M would appear on each line due to the difference between Windows and Linux. ![image](https://github.com/neovide/neovide/assets/31800073/51d0aa39-0f7a-4628-a95d-900cc04dab48) I also tried...

I also tried close ` vim.opt.clipboard = "unnamedplus" `, and it comes again ![image](https://github.com/neovide/neovide/assets/31800073/cbc23ecc-069e-4455-9fae-18a9bd3ff608)

Oh, it seems that things are not that simple. After I close all of the `vim.opt.clipboard = "unnamedplus" `, I still cannot use ` :q` to exit. ![image](https://github.com/neovide/neovide/assets/31800073/f02229c1-8f93-4208-ba68-b446e38272b1)

Thank you for your dedication to this project!❤️

i have the same problem, it seems like there will be scaling issues in the part between the two monitors