Open jungkeun9 opened 3 months ago
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?
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.
Environment
Description
When running vifm in gvim
:Vifm
, the screen is broken if the path or file name includes Korean characters. termwintypewinpty
orconpty
has same issue.