On Sun, Oct 9, 2022 at 12:45 PM Bram Moolenaar <[email protected]> wrote: > > > Tony wrote: > > > Whatever I do, my Vim executables come now out with -rightleft and > > -arabic (since patchlevel 700 maybe?). > > > > These features used to work well enough, and that is the reason why I > > haven't been filing bug reports or posting feedback about them. Now I > > see that at lines 237 to 247 of feature.h, both FEAT_RIGHTLEFT and > > FEAT_ARABIC are now forcibly undefined even if they had been defined > > earlier (and even in Huge builds) on the pretext that no bug reports > > and no feedback have been seen about them recently. Configure > > arguments --enable-rightleft and --enable-arabic also have no effect. > > That was intentional. I asked around about people using the +rightleft > feature and got no response. Since I suspected the message wasn't read > I have disabled the features, but the code is still there. > > I have been wondering how well the right-left support works, since there > were no bug fixes in that area while there must have been changes and > features that interfere. The code has many #ifdefs for this, thus if > it's not used then I rather get rid of it. But if, as you say, it works > well enough then it's worth keeping. > > I'll keep them disabled for a few more days, hopefully that triggers > useful feedback.
I can't believe that I'm the only one using these Vim features, because I expect that: • anyone writing in Hebrew, even occasionally, would need +rightleft; • anyone wriling in Arabic (or Farsi or Urdu or...), even occasionally, would need both +rightleft and +arabic. I remember when Nadim added the +arabic feature, and I helped him test it, especially at first. I think there has been an occasional change as successive Unicode versions defined new RTL characters. These changes may have gone relatively unnoticed by people who don't use them, but I can assure you that, with its known limitations such as not offering true-bidi except in a bidi terminal such as mlterm, the +arabic feature is quite usable, and I expect that +rightleft is even better for writing Hebrew (where +arabic is unnecessary because letters usually stand apart from each other). > > > Similarly, keymaps work well, and I wonder why they have been > > relegated to the Huge build. IMHO, keymaps (and possibly langmaps, > > which I don't use because I am lucky enough to have a mother languague > > using the Latin alphabet) are an essential feature when working with > > non-Latin scripts. I have taken the trouble to write owncoded keymaps > > for both Russian (Cyrillic) and Arabic, but now my workhouse Big build > > (downgraded to Normal level) can't use them anymore. They used to be > > usable with a Big build but now a Huge build (with, from my point of > > view, lots of unneeded ballast) is required. > > It is rather arbitrary. I moved features related to highlighting to the > normal build, and features related to natural language support to the > huge build. Now we have three builds that are different enough to > justify their existence. You can pick the normal build and cherry-pick > some features, or use the huge build and disable features that you don't > want. However, +multi_byte was made unconditional (moved to Tiny) some time ago. Isn't that natural language support too? OTOH, Unicode support is becoming more and more universal these days, especially on Linux (but AFAIR not in your own email client as configured). Best regards, Tony. -- -- You received this message from the "vim_dev" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/CAJkCKXt00UNUM6%3DbyH%2BSHyLkQ5aWmz3EbkLoxLBSD7mEkChzxA%40mail.gmail.com.
