{"thread":{"id":"41879","subject":"Problem with Integrated Vim Editor on Win 10","startedAt":"2016-03-31T00:07:27Z","lastAt":"2016-03-31T18:59:00Z","messageCount":8,"participants":["Zachary Turner","Theo Niessink","Peter Olsson","Dennis Kaarsemaker","Philip Oakley","Junio C Hamano","Konstantin Khomoutov"],"isPatch":false,"patchVersion":null,"patchTotal":null},"messages":[{"id":"282280","messageId":"CAAErz9i1=EOemq2qNijRwgY6MNmPJRhV+mFfeD1FZa5uPwvCJw@mail.gmail.com","threadId":"41879","inReplyTo":null,"subject":"Problem with Integrated Vim Editor on Win 10","fromName":"Zachary Turner","fromEmail":"zturner@google.com","sentAt":"2016-03-31T00:07:27Z","receivedAt":"2016-03-31T00:07:27Z","isPatch":false,"sender":{"key":"zturner@google.com","avatar":null},"body":"Hi, just recently I installed the latest build of Windows 10 of my\nmachine. This is my second Win10 machine. On the other I am using git\n2.7.0.windows.1 and everything is working just fine.\n\nOn the second machine I am using git 2.8.0.windows.1 and vim does not\nwork. I sent a bug report to bugs@vim.org, but frankly I don't know whose\nbug this is, so I'm including it here as well.\n\nThe problem is that vim is just a black screen when git launches it. If I\nmash enough keys eventually I see something that resembles vim output at\nthe bottom, but I can't actually use it.\n\nI tried going into program files\\git\\usr\\bin and just running vim.exe.\nAgain, black screen. If I press enter about 10 times I can see the\nintroduction screen. Then if I press : about 10-20 times it will go into\ncommand mode and a single : appears. after pressing a few more keys all\nthe rest of the :s appear. Basically, everything is completely unusable.\n\nI tried downloading vim 7.4 from www.vim.org, and low and behold, it\nworks. For now I've replaced the copy of vim.exe that ships with git with\nthe copy from www.vim.org. But this leaves me nervous that something is\nseriously wrong.\n\nHas anyone seen anything like this before, or have any ideas how I might\nbetter diagnose this?\n"},{"id":"282295","messageId":"loom.20160331T075527-999@post.gmane.org","threadId":"41879","inReplyTo":"CAAErz9i1=EOemq2qNijRwgY6MNmPJRhV+mFfeD1FZa5uPwvCJw@mail.gmail.com","subject":"Re: Problem with Integrated Vim Editor on Win 10","fromName":"Theo Niessink","fromEmail":"theo@taletn.com","sentAt":"2016-03-31T06:03:10Z","receivedAt":"2016-03-31T06:03:10Z","isPatch":false,"sender":{"key":"theo@taletn.com","avatar":"https://avatars.githubusercontent.com/u/5729397?v=4"},"body":"Zachary Turner google.com> writes:\n\n> Has anyone seen anything like this before, or have any ideas how I might\n> better diagnose this?\n\nNot before, but I can confirm this issue on Win10, and reportedly on Win7 as\nwell. Actually I thought this was a Git for Windows specific issue, so I\nreported it on GitHub; it didn't occur to me that it could be a VIM issue. So\nI guess you have already diagnosed this better than I did...\n"},{"id":"282296","messageId":"loom.20160331T083046-590@post.gmane.org","threadId":"41879","inReplyTo":"CAAErz9i1=EOemq2qNijRwgY6MNmPJRhV+mFfeD1FZa5uPwvCJw@mail.gmail.com","subject":"Re: Problem with Integrated Vim Editor on Win 10","fromName":"Peter Olsson","fromEmail":"peter@olssononline.se","sentAt":"2016-03-31T06:33:26Z","receivedAt":"2016-03-31T06:33:26Z","isPatch":false,"sender":{"key":"peter@olssononline.se","avatar":null},"body":"Zachary Turner google.com> writes:\n\n> \n> Hi, just recently I installed the latest build of Windows 10 of my\n> machine. This is my second Win10 machine. On the other I am using git\n> 2.7.0.windows.1 and everything is working just fine.\n> \n> On the second machine I am using git 2.8.0.windows.1 and vim does not\n> work. I sent a bug report to bugs vim.org, but frankly I don't \nknow whose\n> bug this is, so I'm including it here as well.\n> \n> The problem is that vim is just a black screen when git launches it. \nIf I\n> mash enough keys eventually I see something that resembles vim output \nat\n> the bottom, but I can't actually use it.\n> \n> I tried going into program files\\git\\usr\\bin and just running vim.exe.\n> Again, black screen. If I press enter about 10 times I can see the\n> introduction screen. Then if I press : about 10-20 times it will go \ninto\n> command mode and a single : appears. after pressing a few more keys \nall\n> the rest of the :s appear. Basically, everything is completely \nunusable.\n> \n> I tried downloading vim 7.4 from www.vim.org, and low and behold, it\n> works. For now I've replaced the copy of vim.exe that ships with git \nwith\n> the copy from www.vim.org. But this leaves me nervous that something \nis\n> seriously wrong.\n> \n> Has anyone seen anything like this before, or have any ideas how I \nmight\n> better diagnose this?\n> \n\n\nSame problem here, but on Windows 7. I'm pretty sure that this was \nintroduced in version 2.8.0 for Windows. Before upgrading, I used the \nlatest 2.7 version and it worked as expected.\n\nI'm not sure where we should report this?\n\n/Peter\n"},{"id":"282297","messageId":"1459406979.21328.14.camel@kaarsemaker.net","threadId":"41879","inReplyTo":"loom.20160331T083046-590@post.gmane.org","subject":"Re: Problem with Integrated Vim Editor on Win 10","fromName":"Dennis Kaarsemaker","fromEmail":"dennis@kaarsemaker.net","sentAt":"2016-03-31T06:49:39Z","receivedAt":"2016-03-31T06:49:39Z","isPatch":false,"sender":{"key":"dennis@kaarsemaker.net","avatar":"https://avatars.githubusercontent.com/u/200649?v=4"},"body":"On do, 2016-03-31 at 06:33 +0000, Peter Olsson wrote:\n> I'm not sure where we should report this?\n\nWhile the git-for-windows maintainer does read this list, git-for\n-windows specific issues should be reported in its issue tracker on\nGitHub.\n\nIt looks like this issue has been reported already:\nhttps://github.com/git-for-windows/git/issues/711\n\n-- \nDennis Kaarsemaker\nhttp://www.kaarsemaker.net\n"},{"id":"282348","messageId":"CAAErz9jeLPU+QocSKNssknoJdZoi4Sq0YfZiNnpf4wD70JKQUQ@mail.gmail.com","threadId":"41879","inReplyTo":"CAAErz9i1=EOemq2qNijRwgY6MNmPJRhV+mFfeD1FZa5uPwvCJw@mail.gmail.com","subject":"Re: Problem with Integrated Vim Editor on Win 10","fromName":"Zachary Turner","fromEmail":"zturner@google.com","sentAt":"2016-03-31T17:20:28Z","receivedAt":"2016-03-31T17:20:28Z","isPatch":false,"sender":{"key":"zturner@google.com","avatar":null},"body":"I dug into this some more, and as surprising as it is, I believe the\nrelease of Git 2.8.0 is just busted. I had an installer for 2.7.0\nlying around, so after uninstalling 2.8.0 and re-installing 2.7.0,\neverything works fine.\n\nI'm not terribly active in the Git community so I don't know what the\nprocedure is for things like this, but this seems like a fairly\nserious regression. Suggestions on how to proceed?\n\nOn Wed, Mar 30, 2016 at 5:07 PM, Zachary Turner wrote:\n> Hi, just recently I installed the latest build of Windows 10 of my\n> machine. This is my second Win10 machine. On the other I am using git\n> 2.7.0.windows.1 and everything is working just fine.\n>\n> On the second machine I am using git 2.8.0.windows.1 and vim does not\n> work. I sent a bug report to bugs@vim.org, but frankly I don't know whose\n> bug this is, so I'm including it here as well.\n>\n> The problem is that vim is just a black screen when git launches it. If I\n> mash enough keys eventually I see something that resembles vim output at\n> the bottom, but I can't actually use it.\n>\n> I tried going into program files\\git\\usr\\bin and just running vim.exe.\n> Again, black screen. If I press enter about 10 times I can see the\n> introduction screen. Then if I press : about 10-20 times it will go into\n> command mode and a single : appears. after pressing a few more keys all\n> the rest of the :s appear. Basically, everything is completely unusable.\n>\n> I tried downloading vim 7.4 from www.vim.org, and low and behold, it\n> works. For now I've replaced the copy of vim.exe that ships with git with\n> the copy from www.vim.org. But this leaves me nervous that something is\n> seriously wrong.\n>\n> Has anyone seen anything like this before, or have any ideas how I might\n> better diagnose this?\n"},{"id":"289662","messageId":"20160331204802.375a9614be32168c735a185f@domain007.com","threadId":"41879","inReplyTo":"CAAErz9jeLPU+QocSKNssknoJdZoi4Sq0YfZiNnpf4wD70JKQUQ@mail.gmail.com","subject":"Re: Problem with Integrated Vim Editor on Win 10","fromName":"Konstantin Khomoutov","fromEmail":"kostix+git@007spb.ru","sentAt":"2016-03-31T17:48:02Z","receivedAt":"2016-03-31T17:48:02Z","isPatch":false,"sender":{"key":"kostix+git@007spb.ru","avatar":null},"body":"On Thu, 31 Mar 2016 10:20:28 -0700\nZachary Turner wrote:\n\n> I dug into this some more, and as surprising as it is, I believe the\n> release of Git 2.8.0 is just busted. I had an installer for 2.7.0\n> lying around, so after uninstalling 2.8.0 and re-installing 2.7.0,\n> everything works fine.\n> \n> I'm not terribly active in the Git community so I don't know what the\n> procedure is for things like this, but this seems like a fairly\n> serious regression. Suggestions on how to proceed?\n[...]\n\nThe GfW maintainer had already spotted the bug (in the msys2-runtime,\nIUUC) like some two hours ago -- see the bug #711 in the GfW tracker.\n\nI'm pretty sure a fix will result in a corrected installer being\nreleased. If you can't wait for it for some reason and have to use\n2.8.0, you could build GfW from the sources with the commit I mentioned\nhaving been reverted before the build).\n"},{"id":"282366","messageId":"3130A15B06774B23AF4F56D4939918F1@PhilipOakley","threadId":"41879","inReplyTo":"CAAErz9jeLPU+QocSKNssknoJdZoi4Sq0YfZiNnpf4wD70JKQUQ@mail.gmail.com","subject":"Re: Problem with Integrated Vim Editor on Win 10","fromName":"Philip Oakley","fromEmail":"philipoakley@iee.org","sentAt":"2016-03-31T18:41:44Z","receivedAt":"2016-03-31T18:41:44Z","isPatch":false,"sender":{"key":"philipoakley@iee.email","avatar":"https://avatars.githubusercontent.com/u/914343?v=4"},"body":"From: \"Zachary Turner\" \n>I dug into this some more, and as surprising as it is, I believe the\n> release of Git 2.8.0 is just busted. I had an installer for 2.7.0\n> lying around, so after uninstalling 2.8.0 and re-installing 2.7.0,\n> everything works fine.\n>\n> I'm not terribly active in the Git community so I don't know what the\n> procedure is for things like this, but this seems like a fairly\n> serious regression. Suggestions on how to proceed?\n\nsee https://github.com/git-for-windows/git/issues/711#issuecomment-204003950\n\"Indeed, the culprit is git-for-windows/msys2-runtime@7346568 and reverting \nit fixes the issue. Will continue tomorrow.\" @dscho\n\n\n>\n> On Wed, Mar 30, 2016 at 5:07 PM, Zachary Turner \n> wrote:\n>> Hi, just recently I installed the latest build of Windows 10 of my\n>> machine. This is my second Win10 machine. On the other I am using git\n>> 2.7.0.windows.1 and everything is working just fine.\n>>\n>> On the second machine I am using git 2.8.0.windows.1 and vim does not\n>> work. I sent a bug report to bugs@vim.org, but frankly I don't know whose\n>> bug this is, so I'm including it here as well.\n>>\n>> The problem is that vim is just a black screen when git launches it. If I\n>> mash enough keys eventually I see something that resembles vim output at\n>> the bottom, but I can't actually use it.\n>>\n>> I tried going into program files\\git\\usr\\bin and just running vim.exe.\n>> Again, black screen. If I press enter about 10 times I can see the\n>> introduction screen. Then if I press : about 10-20 times it will go into\n>> command mode and a single : appears. after pressing a few more keys all\n>> the rest of the :s appear. Basically, everything is completely unusable.\n>>\n>> I tried downloading vim 7.4 from www.vim.org, and low and behold, it\n>> works. For now I've replaced the copy of vim.exe that ships with git with\n>> the copy from www.vim.org. But this leaves me nervous that something is\n>> seriously wrong.\n>>\n>> Has anyone seen anything like this before, or have any ideas how I might\n>> better diagnose this?\n> --\n> To unsubscribe from this list: send the line \"unsubscribe git\" in\n> the body of a message to majordomo@vger.kernel.org\n> More majordomo info at http://vger.kernel.org/majordomo-info.html\n> \n"},{"id":"282370","messageId":"xmqqtwjmmq2z.fsf@gitster.mtv.corp.google.com","threadId":"41879","inReplyTo":"CAAErz9jeLPU+QocSKNssknoJdZoi4Sq0YfZiNnpf4wD70JKQUQ@mail.gmail.com","subject":"Re: Problem with Integrated Vim Editor on Win 10","fromName":"Junio C Hamano","fromEmail":"gitster@pobox.com","sentAt":"2016-03-31T18:59:00Z","receivedAt":"2016-03-31T18:59:00Z","isPatch":false,"sender":{"key":"gitster@pobox.com","avatar":"https://avatars.githubusercontent.com/u/54884?v=4"},"body":"Zachary Turner writes:\n\n> I'm not terribly active in the Git community so I don't know what the\n> procedure is for things like this, but this seems like a fairly\n> serious regression. Suggestions on how to proceed?\n\nWhile the git-for-windows folks do read this list, git-for-windows\nspecific issues should be reported in its issue tracker on GitHub.\n\nIt looks like this issue has been reported already:\nhttps://github.com/git-for-windows/git/issues/711\n"}]}