From: Peter Olsson <peter@olssononline.se>
To: git@vger.kernel.org
Subject: Re: Problem with Integrated Vim Editor on Win 10
Date: Thu, 31 Mar 2016 06:33:26 +0000 (UTC) [thread overview]
Message-ID: <loom.20160331T083046-590@post.gmane.org> (raw)
In-Reply-To: CAAErz9i1=EOemq2qNijRwgY6MNmPJRhV+mFfeD1FZa5uPwvCJw@mail.gmail.com
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
next prev parent reply other threads:[~2016-03-31 6:35 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
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 [this message]
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
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=loom.20160331T083046-590@post.gmane.org \
--to=peter@olssononline.se \
--cc=git@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
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.