Skip to content
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

If there are Korean characters in the path or file name, the screen will be broken. #98

Open
jungkeun9 opened this issue Jul 20, 2024 · 3 comments

Comments

@jungkeun9
Copy link

Environment

  • Windows 11
  • gVim 9.1
  • vifm / vifm.vim

Description

When running vifm in gvim :Vifm, the screen is broken if the path or file name includes Korean characters.
termwintype winpty or conpty has same issue.

스크린샷 2024-07-21 024623

@xaizek
Copy link
Member

xaizek commented Jul 20, 2024

Do you experience similar issues when running Vifm outside of gVim?

Also, which path/filename are you talking about? Current working directory of Vim, Vifm or something else?

@jungkeun9
Copy link
Author

  • There's no issue when running outside of gVim (tested on Windows Terminal v1.20.11781.0)

스크린샷 2024-07-21 140659

  • There's no issue when Vifm pane has only English characters. But when either side of pane has Hangul(Korean characters), the screen is broken.

@xaizek
Copy link
Member

xaizek commented Jul 21, 2024

There's no issue when running outside of gVim (tested on Windows Terminal v1.20.11781.0)

Judging by the screenshot it's not as bad, but there is still an issue.

vifm.vim doesn't handle terminal in any real way, so this is either a problem in Vifm/pdcurses which gets worse inside of gVim or an issue in gVim (in combination with Vifm's output or not). I could reproduce it using :terminal command and then running vifm, while output of dir doesn't cause such weird effects, but there are also no colors which could play a role. At the same time, using the same filename on Linux works without any issues, but I don't know if Vim uses the same parser on Linux as on Windows (not very likely).

Need to determine more precisely what causes this before judging if it can be addressed and where/how.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

2 participants