Actually you might look at this question and let me know if it can be adapted to be basically: here's all the ways I could run vim, is there a right way? http://superuser.com/questions/1016899/windows-10s-story-for-unixhttps://superuser.com/questions/1016899/windows-10s-story-for-unix
Actually you might look at this question and let me know if it can be adapted to be basically: here's all the ways I could run vim, is there a right way? http://superuser.com/questions/1016899/windows-10s-story-for-unix
Actually you might look at this question and let me know if it can be adapted to be basically: here's all the ways I could run vim, is there a right way? https://superuser.com/questions/1016899/windows-10s-story-for-unix
Running Vim on Windows: is there a best way?
Can I even ask about how to "best" install Vim on windows? I generally a have a unix problem there... and it affects vim in that gVim mostly works, but then some odd things aren't working (like tab completing help topics nor commands nor files) and running vim in the cmd.exe messes up the colors very much (compared to in Mintty, but that's another issue where I have multiple vims around now just because some environments come with their own).
Actually you might look at this question and let me know if it can be adapted to be basically: here's all the ways I could run vim, is there a right way? http://superuser.com/questions/1016899/windows-10s-story-for-unix
Oh and that's deleted now. Allow me to um... include the text here for reference:
What's the story for Unix on Windows 10?
I recently moved from MacOS X 10.11 to Windows 10, and am sorely missing the one true unix installation for the operating system.
I ask due to the following experiences:
- I installed git for windows and got a little compact bit of unix in
C:\Program Files\Git\git-bash.exewhich runs
- mintty using
- mingw64 running with
bindevetctmpusrconfusingly mounted out of the aforementioned directory yet there being amingw64directory that similarly containsbinetcliblibexecsharesslthat don't seem to get mounted and refers toC:\Users\MyUserName\as the home dir.- If I run
vimit runs the/usr/bin/vimcontained version that's build differently than the windows version, and opening:e %MYVIMRCopens~/.vim/vimrc- It maps
C:to/c/
- Cygwin which runs
- mintty too, out of
C:\cygwin\withbindevetchomelibsbintmpusrvarin it where the home dir is within thathomeinstead of my windows homedir.- If I run
vimit hangs until I press control-c, which closes the window too.- It maps
C:to/cygdrive/c/- It is noticeably slower, even at the prompt.
- Github Desktop for Windows, which has an executable called
git shellwhich can be configured to runbashand then runs a prompt that is not mintty using
- mingw64 but out of somewhere like
C:\Users\MyUserName\AppData\Local\GitHub\PortableGit_ahashofacommit\- It maps
C:to/c/- If I run
vimit runs the windows installed version that read:e $MYVIMRCfrom~/vimfiles/vimrc/
- Gnu on Windows, which gives some exe files in a
C:\Program Files (x86)\Gow\binthese can run in any of the previous environments and also the Windows cmd.exe prompt/shell.
- Fast, easy to install, but quite limited in adding anything onto them.
- Run with
cmd.exeit mapsC:toC:.- Run with
cmd.exevimruns in the window with off colors and reads:e $MYVIMRCfrom~/vimfiles/vimrc.
- Vim for Windows, which can run
gVimright from the start menu, orgvim/vimfrom the command prompt.
- It reads
:e $MYVIMRCfrom~/vimfiles/vimrc/- gVim maps
C:to/I won't get into the oddness around supposed cross-platform software ranging from Eclipse, Visual Studio Code, to MySQL, and more niche items like MIT-Scheme. I'll just say they're imperfect even if the first two are nearly well polished. The Java environment is relatively interoperable, but retains a preference for a Unix style that seems un-native.
It gets even more confusing as one moves forward trying to install and run something like Apache Drill or another generally for unix tool which has a Windows version. You can't run it in anything but the cmd.exe prompt, but in that prompt it unhooks input accidentally piping the input to the prompt. For example.
So were is the unifying Unix toolset for windows? Is it still Cygwin, if so, why is it so slow and painful and hard to add non-standard packages to? Does everyone just run Linux/FreNetBSD/Minix in a virtual machine or what's going on that this mess is the new normal? Microsoft HAD Windows Services for Unix, but that was neither here nor there and it's deprecated. Does Microsoft have no reason to try making an official way to get, or build ported unix software in some light semi-virtualized posix way?