Le 2014-04-21, Bram Moolenaar <[email protected]> a écrit : > > > > Yet I wonder if the current hack with ASCII characters is really useful. > > Is there any performance test to check if a simpler behaviour wouldn't be > > suitable, at least for modern desktop installations? > > As the code comment mentions spaces, maybe it should be restricted to > > blank lines? > > This stuff is too complicated to guess what works best. > Any changes need to be tested with various GTK versions and with > different display drivers to check the speed. Even modern desktops > sometimes have slow graphics (using generic drivers instead of > proprietary ones). > > Note the remark about drawing the cursor, check that the test doesn't > change when moving the cursor over it.
It was clear this stuff was complicated, that's why I opted for a minimal change. It didn't have any visible effect on my desktop, and now I can use some fonts that were mangled in gvim before (mangled on lines with no non-ASCII chars!). > Perhaps we should add an option to disable the optimization? In my humble opinion, removing the current optimization hack should be a long-term goal. The optimization adds complexity to the display code, with various side-effects. And as Pango and such have evolved, I don't know if there is still a need for a distinct display routine on ASCII lines. Thanks -- François -- -- 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]. For more options, visit https://groups.google.com/d/optout.
