On Mon, Jul 3, 2017 at 7:50 AM, mattn <[email protected]> wrote: > On Monday, July 3, 2017 at 6:16:51 PM UTC+9, Bram Moolenaar wrote: >> Yasuhiro Matsumoto wrote: >> >> > I have implementation (but PoC/WIP) that works on Windows. >> > >> > https://qiita-image-store.s3.amazonaws.com/0/665/67e1a2e1-c2dc-847e-20b6-5b26a0f62b89.gif >> > >> > This is in vim/terminal branch in my repository. >> > >> > https://github.com/mattn/vim/tree/terminal >> >> Interesting. What kind of terminal does it pretend to be? With >> libvterm it's like an xterm. On MS-Windows commands expect to be >> running in a console, that is quite different. So only programs ported >> from Unix would run in libvterm. > > This is not terminal. This is gvim.exe (with guioptions= ). This doesn't any > external libraries. >
Yes, but your terminal implementation must adhere to some standard. Most Unix derived virtual terminals use inline control characters to manipulate the state of the terminal. On Windows, a terminal is created by operating system code as a desktop window and doesn't implement a control code standard. As it always existed as some form of abstraction and never copied physical hardware, there is a set of system calls that interacts with the same code that creates a terminal as a desktop window.[1] This is what I was trying to point out when I mentioned Cygwin. The project may have merit (and I think it does) but it is far less useful for all Windows users of Vim based on assumptions that are being built into it. [1] You can make cmd.exe or powershell.exe interpret most VT control codes but this doesn't do anything for you if you need to make a Windows program run in a VT environment. -- -- 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.
