All of lore.kernel.org
 help / color / mirror / Atom feed
* Problem with Integrated Vim Editor on Win 10
@ 2016-03-31  0:07 Zachary Turner
  2016-03-31  6:03 ` Theo Niessink
                   ` (2 more replies)
  0 siblings, 3 replies; 8+ messages in thread
From: Zachary Turner @ 2016-03-31  0:07 UTC (permalink / raw)
  To: Git Mailing List

Hi, just recently I installed the latest build of Windows 10 of my
machine. This is my second Win10 machine. On the other I am using git
2.7.0.windows.1 and everything is working just fine.

On the second machine I am using git 2.8.0.windows.1 and vim does not
work. I sent a bug report to bugs@vim.org, but frankly I don't know whose
bug this is, so I'm including it here as well.

The problem is that vim is just a black screen when git launches it. If I
mash enough keys eventually I see something that resembles vim output at
the bottom, but I can't actually use it.

I tried going into program files\git\usr\bin and just running vim.exe.
Again, black screen. If I press enter about 10 times I can see the
introduction screen. Then if I press : about 10-20 times it will go into
command mode and a single : appears. after pressing a few more keys all
the rest of the :s appear. Basically, everything is completely unusable.

I tried downloading vim 7.4 from www.vim.org, and low and behold, it
works. For now I've replaced the copy of vim.exe that ships with git with
the copy from www.vim.org. But this leaves me nervous that something is
seriously wrong.

Has anyone seen anything like this before, or have any ideas how I might
better diagnose this?

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Problem with Integrated Vim Editor on Win 10
  2016-03-31  0:07 Problem with Integrated Vim Editor on Win 10 Zachary Turner
@ 2016-03-31  6:03 ` Theo Niessink
  2016-03-31  6:33 ` Peter Olsson
  2016-03-31 17:20 ` Zachary Turner
  2 siblings, 0 replies; 8+ messages in thread
From: Theo Niessink @ 2016-03-31  6:03 UTC (permalink / raw)
  To: git

Zachary Turner <zturner <at> google.com> writes:

> Has anyone seen anything like this before, or have any ideas how I might
> better diagnose this?

Not before, but I can confirm this issue on Win10, and reportedly on Win7 as
well. Actually I thought this was a Git for Windows specific issue, so I
reported it on GitHub; it didn't occur to  me that it could be a VIM issue. So
I guess you have already diagnosed this better than I did...

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Problem with Integrated Vim Editor on Win 10
  2016-03-31  0:07 Problem with Integrated Vim Editor on Win 10 Zachary Turner
  2016-03-31  6:03 ` Theo Niessink
@ 2016-03-31  6:33 ` Peter Olsson
  2016-03-31  6:49   ` Dennis Kaarsemaker
  2016-03-31 17:20 ` Zachary Turner
  2 siblings, 1 reply; 8+ messages in thread
From: Peter Olsson @ 2016-03-31  6:33 UTC (permalink / raw)
  To: git

Zachary Turner <zturner <at> google.com> writes:

> 
> Hi, just recently I installed the latest build of Windows 10 of my
> machine. This is my second Win10 machine. On the other I am using git
> 2.7.0.windows.1 and everything is working just fine.
> 
> On the second machine I am using git 2.8.0.windows.1 and vim does not
> work. I sent a bug report to bugs <at> vim.org, but frankly I don't 
know whose
> bug this is, so I'm including it here as well.
> 
> The problem is that vim is just a black screen when git launches it. 
If I
> mash enough keys eventually I see something that resembles vim output 
at
> the bottom, but I can't actually use it.
> 
> I tried going into program files\git\usr\bin and just running vim.exe.
> Again, black screen. If I press enter about 10 times I can see the
> introduction screen. Then if I press : about 10-20 times it will go 
into
> command mode and a single : appears. after pressing a few more keys 
all
> the rest of the :s appear. Basically, everything is completely 
unusable.
> 
> I tried downloading vim 7.4 from www.vim.org, and low and behold, it
> works. For now I've replaced the copy of vim.exe that ships with git 
with
> the copy from www.vim.org. But this leaves me nervous that something 
is
> seriously wrong.
> 
> Has anyone seen anything like this before, or have any ideas how I 
might
> better diagnose this?
> 


Same problem here, but on Windows 7. I'm pretty sure that this was 
introduced in version 2.8.0 for Windows. Before upgrading, I used the 
latest 2.7 version and it worked as expected.

I'm not sure where we should report this?

/Peter

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Problem with Integrated Vim Editor on Win 10
  2016-03-31  6:33 ` Peter Olsson
@ 2016-03-31  6:49   ` Dennis Kaarsemaker
  0 siblings, 0 replies; 8+ messages in thread
From: Dennis Kaarsemaker @ 2016-03-31  6:49 UTC (permalink / raw)
  To: Peter Olsson, git

On do, 2016-03-31 at 06:33 +0000, Peter Olsson wrote:
> I'm not sure where we should report this?

While the git-for-windows maintainer does read this list, git-for
-windows specific issues should be reported in its issue tracker on
GitHub.

It looks like this issue has been reported already:
https://github.com/git-for-windows/git/issues/711

-- 
Dennis Kaarsemaker
http://www.kaarsemaker.net

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Problem with Integrated Vim Editor on Win 10
  2016-03-31  0:07 Problem with Integrated Vim Editor on Win 10 Zachary Turner
  2016-03-31  6:03 ` Theo Niessink
  2016-03-31  6:33 ` Peter Olsson
@ 2016-03-31 17:20 ` Zachary Turner
  2016-03-31 17:48   ` Konstantin Khomoutov
                     ` (2 more replies)
  2 siblings, 3 replies; 8+ messages in thread
From: Zachary Turner @ 2016-03-31 17:20 UTC (permalink / raw)
  To: Git Mailing List

I dug into this some more, and as surprising as it is, I believe the
release of Git 2.8.0 is just busted.  I had an installer for 2.7.0
lying around, so after uninstalling 2.8.0 and re-installing 2.7.0,
everything works fine.

I'm not terribly active in the Git community so I don't know what the
procedure is for things like this, but this seems like a fairly
serious regression.  Suggestions on how to proceed?

On Wed, Mar 30, 2016 at 5:07 PM, Zachary Turner <zturner@google.com> wrote:
> Hi, just recently I installed the latest build of Windows 10 of my
> machine. This is my second Win10 machine. On the other I am using git
> 2.7.0.windows.1 and everything is working just fine.
>
> On the second machine I am using git 2.8.0.windows.1 and vim does not
> work. I sent a bug report to bugs@vim.org, but frankly I don't know whose
> bug this is, so I'm including it here as well.
>
> The problem is that vim is just a black screen when git launches it. If I
> mash enough keys eventually I see something that resembles vim output at
> the bottom, but I can't actually use it.
>
> I tried going into program files\git\usr\bin and just running vim.exe.
> Again, black screen. If I press enter about 10 times I can see the
> introduction screen. Then if I press : about 10-20 times it will go into
> command mode and a single : appears. after pressing a few more keys all
> the rest of the :s appear. Basically, everything is completely unusable.
>
> I tried downloading vim 7.4 from www.vim.org, and low and behold, it
> works. For now I've replaced the copy of vim.exe that ships with git with
> the copy from www.vim.org. But this leaves me nervous that something is
> seriously wrong.
>
> Has anyone seen anything like this before, or have any ideas how I might
> better diagnose this?

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Problem with Integrated Vim Editor on Win 10
  2016-03-31 17:20 ` Zachary Turner
@ 2016-03-31 17:48   ` Konstantin Khomoutov
  2016-03-31 18:41   ` Philip Oakley
  2016-03-31 18:59   ` Junio C Hamano
  2 siblings, 0 replies; 8+ messages in thread
From: Konstantin Khomoutov @ 2016-03-31 17:48 UTC (permalink / raw)
  To: Zachary Turner; +Cc: Git Mailing List

On Thu, 31 Mar 2016 10:20:28 -0700
Zachary Turner <zturner@google.com> wrote:

> I dug into this some more, and as surprising as it is, I believe the
> release of Git 2.8.0 is just busted.  I had an installer for 2.7.0
> lying around, so after uninstalling 2.8.0 and re-installing 2.7.0,
> everything works fine.
> 
> I'm not terribly active in the Git community so I don't know what the
> procedure is for things like this, but this seems like a fairly
> serious regression.  Suggestions on how to proceed?
[...]

The GfW maintainer had already spotted the bug (in the msys2-runtime,
IUUC) like some two hours ago -- see the bug #711 in the GfW tracker.

I'm pretty sure a fix will result in a corrected installer being
released.  If you can't wait for it for some reason and have to use
2.8.0, you could build GfW from the sources with the commit I mentioned
having been reverted before the build).

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Problem with Integrated Vim Editor on Win 10
  2016-03-31 17:20 ` Zachary Turner
  2016-03-31 17:48   ` Konstantin Khomoutov
@ 2016-03-31 18:41   ` Philip Oakley
  2016-03-31 18:59   ` Junio C Hamano
  2 siblings, 0 replies; 8+ messages in thread
From: Philip Oakley @ 2016-03-31 18:41 UTC (permalink / raw)
  To: Zachary Turner, Git Mailing List

From: "Zachary Turner" <zturner@google.com>
>I dug into this some more, and as surprising as it is, I believe the
> release of Git 2.8.0 is just busted.  I had an installer for 2.7.0
> lying around, so after uninstalling 2.8.0 and re-installing 2.7.0,
> everything works fine.
>
> I'm not terribly active in the Git community so I don't know what the
> procedure is for things like this, but this seems like a fairly
> serious regression.  Suggestions on how to proceed?

see https://github.com/git-for-windows/git/issues/711#issuecomment-204003950
"Indeed, the culprit is git-for-windows/msys2-runtime@7346568 and reverting 
it fixes the issue. Will continue tomorrow." @dscho


>
> On Wed, Mar 30, 2016 at 5:07 PM, Zachary Turner <zturner@google.com> 
> wrote:
>> Hi, just recently I installed the latest build of Windows 10 of my
>> machine. This is my second Win10 machine. On the other I am using git
>> 2.7.0.windows.1 and everything is working just fine.
>>
>> On the second machine I am using git 2.8.0.windows.1 and vim does not
>> work. I sent a bug report to bugs@vim.org, but frankly I don't know whose
>> bug this is, so I'm including it here as well.
>>
>> The problem is that vim is just a black screen when git launches it. If I
>> mash enough keys eventually I see something that resembles vim output at
>> the bottom, but I can't actually use it.
>>
>> I tried going into program files\git\usr\bin and just running vim.exe.
>> Again, black screen. If I press enter about 10 times I can see the
>> introduction screen. Then if I press : about 10-20 times it will go into
>> command mode and a single : appears. after pressing a few more keys all
>> the rest of the :s appear. Basically, everything is completely unusable.
>>
>> I tried downloading vim 7.4 from www.vim.org, and low and behold, it
>> works. For now I've replaced the copy of vim.exe that ships with git with
>> the copy from www.vim.org. But this leaves me nervous that something is
>> seriously wrong.
>>
>> Has anyone seen anything like this before, or have any ideas how I might
>> better diagnose this?
> --
> To unsubscribe from this list: send the line "unsubscribe git" in
> the body of a message to majordomo@vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> 

^ permalink raw reply	[flat|nested] 8+ messages in thread

* Re: Problem with Integrated Vim Editor on Win 10
  2016-03-31 17:20 ` Zachary Turner
  2016-03-31 17:48   ` Konstantin Khomoutov
  2016-03-31 18:41   ` Philip Oakley
@ 2016-03-31 18:59   ` Junio C Hamano
  2 siblings, 0 replies; 8+ messages in thread
From: Junio C Hamano @ 2016-03-31 18:59 UTC (permalink / raw)
  To: Zachary Turner; +Cc: Git Mailing List

Zachary Turner <zturner@google.com> writes:

> I'm not terribly active in the Git community so I don't know what the
> procedure is for things like this, but this seems like a fairly
> serious regression.  Suggestions on how to proceed?

While the git-for-windows folks do read this list, git-for-windows
specific issues should be reported in its issue tracker on GitHub.

It looks like this issue has been reported already:
https://github.com/git-for-windows/git/issues/711

^ permalink raw reply	[flat|nested] 8+ messages in thread

end of thread, other threads:[~2016-06-20 10:07 UTC | newest]

Thread overview: 8+ messages (download: mbox.gz / follow: Atom feed)
-- links below jump to the message on this page --
2016-03-31  0:07 Problem with Integrated Vim Editor on Win 10 Zachary Turner
2016-03-31  6:03 ` Theo Niessink
2016-03-31  6:33 ` Peter Olsson
2016-03-31  6:49   ` Dennis Kaarsemaker
2016-03-31 17:20 ` Zachary Turner
2016-03-31 17:48   ` Konstantin Khomoutov
2016-03-31 18:41   ` Philip Oakley
2016-03-31 18:59   ` Junio C Hamano

This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.