On Wednesday, December 13, 2017 at 7:27:59 PM UTC-8, David Kotchan wrote: > OK I have re-pulled, and am now on the "optimize-directx" branch, which has > latest commit 9af94dbea8389a5e31a946f53d9d7a11561d1456, one commit after the > 0e7d0764 commit you mention above. I will try this branch (at 9af94dbe). [snip] > ...Yes, I will also try gdi-cursor branch. At time of my pull, latest commit > is 192bd7e9e871b5aacb4c1142fe505aaf5bb72dc6. > [snip] > Well, I will compile these and report back. Again, thank you for your time > and effort on this problem!
Hi Ken I am sorry to report, neither the "optimize-directx" (also with scrlines:1) nor the "gdi-cursor" (with gdicursor:1) has helped the problem on my Win10 Enterprise system :-/ I have posted a video showing the speed difference (demo), if you are interested. https://onedrive.live.com/?id=6870FB040B1C655B%21700&cid=6870FB040B1C655B The first Vim is patch 1366; the second Vim is "gdi-cursor". Anyways, I will continue to investigate and perhaps try other compile options. Thank you for your time. --David -- -- 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 vim_dev+unsubscr...@googlegroups.com. For more options, visit https://groups.google.com/d/optout.
