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
Please add BiDi support to Vim #204
Comments
Original comment by |
Original comment by |
It's really needed. Nearly ALL of modern editors support this feature. +1 |
I started gathering the summary gist (like I did with true color one) and linked this issue in it https://gist.github.com/XVilka/a0e49e1c65370ba11c17 |
Full-bidi would IMHO be extremely hard (and therefore error-prone) to implement in Vim, which never was a WYSIWYG text processor but just a plain text editor. The recommended way to have Vim display full-bidi text is to let the terminal take care of it (which also means running Vim in a bidi-capable terminal and not as gvim). The mlterm terminal can do full-bidi, and Vim is aware of it, but you might have to get its source and compile it yourself: e.g. AFAICT my (openSUSE Linux) distro does not have it in its software repositories. See also Best regards, |
For now, as a workaround, I'd |
neatvi already supports it and it works flawlessly for Persian, Arabic, Hebrew, etc. languages even with a non-BIDI terminal. Can we add neatvi BIDI feature to vim? The author of neatvi has already released a patch for this issue here but it seems to be neglected! THere is also a similar request for Nvim project here. |
Please note, recently there was created a working group regarding BiDi support in a console: |
Note, that with the release of GNOME 3.34 the support of BiDi by @egmontkob is available in Gnome Terminal out of the box, which makes testing/implementing it in the other programs, such as Vim way easier. |
I have a problem with Vim in a BiDi supported libvte based terminal like gnome-terminal : Zero width non-joiner (ZWNJ) shows as the unicode escape (<200c>). A workaround is given below which is not great since it hides the ZWNJ and does not join the persian chars: The problem is also mentioned below even though it is not relevant to kitty terminal: |
Original issue reported on code.google.com by
casey.be...@gmail.com
on 9 Mar 2014 at 8:39The text was updated successfully, but these errors were encountered: