On Tuesday, September 12, 2017 at 11:35:19 PM UTC+3, Bram Moolenaar wrote: > Christian wrote: > > > On Fr, 08 Sep 2017, Bram Moolenaar wrote: > > > > > Patch 8.0.1074 > > > Problem: ":term NONE" does not work on MS-Windows. > > > Solution: Make it work. Split "pty" into "pty_in" and "pty_out". > > > (Yasuhiro > > > Matsumoto, closes #2058, closes #2045) > > > Files: runtime/doc/eval.txt, src/channel.c, src/evalfunc.c, > > > src/os_unix.c, src/structs.h, src/terminal.c, > > > src/testdir/test_terminal.vim > > > > Since a couple of days, the vim-win32-installer repository fails to > > provide updated binaries and my guess is, that this patch is the reason. > > It basically started after 8.0.1071. > > > > >From the logfile (e.g. this one: > > https://ci.appveyor.com/project/chrisbra/vim-win32-installer/build/476/job/cp9t262lem4aj5sa > > see also this overview: > > https://ci.appveyor.com/project/chrisbra/vim-win32-installer/history) > > > > It looks like test_terminal hangs infinitely and then appveyor times > > out. Is there anything to make this work again and provide updated > > binaries? > > I have seen this happen when there is a message during startup, which > causes a dialog that is waiting for a click. However, Appveyour passed > for the last builds, thus there must be something in this setup that > causes it. Probably the terminal feature, so you could temporarily > disable that. > > Tried it locally, and can confirm what Charles Cooper mentioned. > Looks strange, using cmd.exe to execute "cmd".
Any updates about this problem? -- -- 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.
