-
-
Notifications
You must be signed in to change notification settings - Fork 5.3k
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
The behavior when specifying 2 for setcellwidths
is different between the GUI version and the CUI version.
#14539
Labels
Comments
This was referenced Apr 13, 2024
zeertzjq
added a commit
to zeertzjq/neovim
that referenced
this issue
Apr 17, 2024
Problem: Cursor wrong after using setcellwidth() in terminal (mikoto2000) Solution: output additional spaces, so the behaviour matches the GUI (mikoto2000) fixes: vim/vim#14539 closes: vim/vim#14540 Fix CUI `setcellwidths` characters draw behavior to same GUI behavior. vim/vim@e20fa59 This is already fixed and tested in Nvim in neovim#28322. Co-authored-by: mikoto2000 <mikoto2000@gmail.com>
zeertzjq
added a commit
to neovim/neovim
that referenced
this issue
Apr 17, 2024
…al (#28391) Problem: Cursor wrong after using setcellwidth() in terminal (mikoto2000) Solution: output additional spaces, so the behaviour matches the GUI (mikoto2000) fixes: vim/vim#14539 closes: vim/vim#14540 Fix CUI `setcellwidths` characters draw behavior to same GUI behavior. vim/vim@e20fa59 This is already fixed and tested in Nvim in #28322. Co-authored-by: mikoto2000 <mikoto2000@gmail.com>
huangyingw
pushed a commit
to huangyingw/neovim
that referenced
this issue
May 31, 2024
…al (neovim#28391) Problem: Cursor wrong after using setcellwidth() in terminal (mikoto2000) Solution: output additional spaces, so the behaviour matches the GUI (mikoto2000) fixes: vim/vim#14539 closes: vim/vim#14540 Fix CUI `setcellwidths` characters draw behavior to same GUI behavior. vim/vim@e20fa59 This is already fixed and tested in Nvim in neovim#28322. Co-authored-by: mikoto2000 <mikoto2000@gmail.com>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Steps to reproduce
test.txt
.Expected behaviour
Same behavior as GUI version.
GUI:
![320875565-7a624485-fe37-411e-9ce5-a6563752c5ce](https://private-user-images.githubusercontent.com/345832/322209537-8f6dfc2e-f96e-48b4-8431-c655ddaef3cb.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkyNjU2MzIsIm5iZiI6MTcxOTI2NTMzMiwicGF0aCI6Ii8zNDU4MzIvMzIyMjA5NTM3LThmNmRmYzJlLWY5NmUtNDhiNC04NDMxLWM2NTVkZGFlZjNjYi5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjI0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyNFQyMTQyMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT05OTNkM2E2MDZhZDNjNDU3MzExNzZkZjMzNDE0ZGM5N2VlZjc3MjFlZDFlOWRmZWRhMzM4NGMwZjFkOTc4MjgzJlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.5lzJ1PyQVKOIpuOIHkjdihYo58_zZvnhb5s2i5x9lY8)
CUI:
![320875299-229a17da-2cfb-45c3-9763-1c4d7b3863e8](https://private-user-images.githubusercontent.com/345832/322209551-513b6100-ed33-4260-9d47-fc6dd7bd2b86.png?jwt=eyJhbGciOiJIUzI1NiIsInR5cCI6IkpXVCJ9.eyJpc3MiOiJnaXRodWIuY29tIiwiYXVkIjoicmF3LmdpdGh1YnVzZXJjb250ZW50LmNvbSIsImtleSI6ImtleTUiLCJleHAiOjE3MTkyNjU2MzIsIm5iZiI6MTcxOTI2NTMzMiwicGF0aCI6Ii8zNDU4MzIvMzIyMjA5NTUxLTUxM2I2MTAwLWVkMzMtNDI2MC05ZDQ3LWZjNmRkN2JkMmI4Ni5wbmc_WC1BbXotQWxnb3JpdGhtPUFXUzQtSE1BQy1TSEEyNTYmWC1BbXotQ3JlZGVudGlhbD1BS0lBVkNPRFlMU0E1M1BRSzRaQSUyRjIwMjQwNjI0JTJGdXMtZWFzdC0xJTJGczMlMkZhd3M0X3JlcXVlc3QmWC1BbXotRGF0ZT0yMDI0MDYyNFQyMTQyMTJaJlgtQW16LUV4cGlyZXM9MzAwJlgtQW16LVNpZ25hdHVyZT0yNWQyNDRjMjc5YTY5OGRhZjcwNmIyMGM2YzAwOTRmMmE3YjQ4YjM5MGY3M2Q4ZTcxYmY1MjQwYTJlZDE3YWM1JlgtQW16LVNpZ25lZEhlYWRlcnM9aG9zdCZhY3Rvcl9pZD0wJmtleV9pZD0wJnJlcG9faWQ9MCJ9.OlsBo8m3FqubUr3EmJ-hr1AKHdWwMRlhIHOeTY0hD2E)
※ Text is drawn up to the yellow arrow, but the cursor moves to the green arrow.
Version of Vim
9.1.309
Environment
We have confirmed that this happens in the following three environments
Environment1:
Environment2:
Environment3:
Logs and stack traces
No response
The text was updated successfully, but these errors were encountered: