Vim in command prompt on Windows 10

27,551

Solution 1

Go to the file location, and double click install.exe. That will open cmd.

If it asks you "Do you want to uninstall", type N and then type D.

Solution 2

Actually I selected 'browse directory' and selected the location of Vim i.e., C:\Program Files (x86)\Vim

You need to locate the directory that contains vim.exe. If you use the default installation options (and latest available version), that would be C:\Program Files (x86)\Vim\vim80.

Note that there's also a 64-bit version of Vim for Windows.

Solution 3

Install vim again and make sure to check the box of "create .bat files" option when installing

Solution 4

It's a problem of the installer on Windows 10!

The installer tries to write some files into C:\WINDOWS, but if you install without administrator privileges, those files cannot be written. However, the rest of the install works and so you think everything is fine.

Try to restart install.exe as an administrator!

Solution 5

unistall everythingn then follow the guide on: https://www.thewindowsclub.com/install-vim-text-editor-on-windows and make sure to get the full installation it will work in the CMD after that make sure to run it as admin i had the same issue

Share:
27,551

Related videos on Youtube

SQR
Author by

SQR

Updated on July 09, 2022

Comments

  • SQR
    SQR almost 2 years

    I wanted to use Vim on the command prompt, but it gave

    vim is not recognized as an internal or external command

    I tried searching for a solution and found that I should edit the user specific environment variable 'path', but it still gives the same error. What can be the solution?

  • Admin
    Admin over 5 years
    Answers should be standalone, without relying on external links. Please edit this answer and put in the relevant details that you feel address the question posed.
  • Barungi Stephen
    Barungi Stephen about 3 years
    How does this magically work ? Yet D is not among the options .
  • Stef
    Stef almost 3 years
    Although this isn't a "proper" answer, this did work for me. Thanks.
  • cBlaine
    cBlaine over 2 years
    The underlying issue wound up being Run As Administrator for me but this helped me to expose it

Related