Firstly I have never heard of ConsoleZ, but if something doesn't work with ConsoleZ but does work with the standard Windows console, then by definition that's a bug in ConsoleZ. CMD and PowerShell are not conclusive measures of compatibility because they don't exercise many of the advanced features of the console, whereas Vim does.
> On Do, 29 Okt 2015, Ken Takata wrote: > > It is obvious that 7.4.851 causes this problem. > > When I wrote the patch, I thought that using > > CreateConsoleScreenBuffer and SetConsoleActiveScreenBuffer is a > > perfect solution to save and restore a console buffer, but now I > > think it was totally wrong because it causes many problems. If Vim's console code was changed to use CreateConsoleScreenBuffer/SetConsoleActiveScreenBuffer, then that change needs to be reverted. I say this even if ConsoleZ were to support these APIs properly. Vim 5.x actually did use CreateConsoleScreenBuffer/SetConsoleActiveScreenBuffer. We changed this in 6.0 to instead do everything with a single console buffer. This was to enable Telnet to work, because Telnet scrapes the console buffer. Anything else that scrapes the console buffer would also need this. >From version6.txt: Win32: Console version didn't work on telnet, because of switching between two console screens. Now use one console screen and save/restore the contents when needed. (Craig Barkhouse) -- -- 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.
