I've been setting up a new Windows 7 64-bit PC. I've installed msysgit git version 1.9.0.msysgit.0, placing both git and git BASH on my normal Windows path. I've also installed ansicon, and am running the 64-bit version.
This is, as near as I can tell, identical to the setup on my old PC; but on the new system I'm not getting coloured output from git (I am getting it from other tools, like rspec), and git is not using a default editor. On my old PC I get coloured output, and git fires up vim when it wants an editor.
I can't immediately find any config differences (the old PC shows blank for git config --global --get color.ui and git config global --get core.editor, and %EDITOR% is not set).
Any suggestions what might be different?
Aha, found it. I needed to change the value of the TERM environment variable.
Setting TERM=msys sorted everything.
Related
I am using Git on Windows with MINGW. I thought what about using WSL insteat for git. I have installed git on WSL (I am using Debian). If I trype git status he show many files of my project as 'modified' in red color.
What does that mean? If I use git diff I don' see any difference in the files. How can I safe switch to use WSL?
On my Windows machine, I have a repository that works nicely with msysgit. But when I try running git status on cygwin, it just hangs, without printing anything until I press Ctrl-C.
How can I investigate this to find out the reason for such behaviour?
The reason for this was the difference in core.autocrlf setting. When install git for windows, I set it to automatically convert line endings in both directions, so the files in the filesystem were actually different from the files saved in git history - but windows git always hid these differences.
Meanwhile, cygwin git was working extremely slow because it detected differences in every line of thousands of text files in my repository.
I have Windows 8.1 on my laptop and I've installed Git. If I type git --version in Windows' command prompt, the result is git version 1.8.5.2.msysgit.0. I can commit and update all the stuff on the server, everything works fine.
At the same time, I'd like to have a GUI for that so I've installed GitHub for Windows. Unfortunately, it does not let me commit my changes as it report that there is an error as suggests opening a shell (also console-like, but looks different from usual Windows' cmd). If I type in that shell git --version I get git version 1.8.4.msysgit.0 so apparently the GUI app uses an older version of git than the one I need, although I have a needed version of Git installed on my computer.
I appreciate any hints on how to make the GUI app to use the new version of git. If any details are still needed, please tell me - I'll provide them asap. Thanks
You will find the git (embedded in G4W -- GitHub for Windows as SLaks mentions) in
%LOCALAPPDATA%\GitHub\Portable_Git_xxxxx\
(See "Can the credentials stored in Github for Windows be shared with the whole operating system?")
You can try and replace that folder by a portable Git, PortableGit-1.8.5.2-preview20131230.7z: once uncompressed, you can rename the folder with the same name 'Portable_Git_xxxxx' and see if that works.
I installed vim fugitive via pathogen plugin. Helptags created the tags for fugitive.
In the next step I set up a brand new git repo with git init, jumped into that folder, created a README.
In gVim I then run :Gstatus but the split window that opens is empty. :Gcommit tells me that the command git is spelled wrong.
I installed Git-1.7.9-preview20120201.exe for Windows 7 64Bit from here:
http://code.google.com/p/msysgit/downloads/list
Can anybody bring me on the right track?
Regards
It seems gitcommand is not in the PATH environment variable. What happens if you invoke git from Windows command prompt?
msysgit installer provides you 3 options:
Use Git Bash only: PATH won't be edited.
Run Git from Windows Command Prompt: it will add Git to your PATH.
Run Git and included Unix tools from the Windows Command Prompt: Git and several Unix tools will be added to your PATH.
So, you can re-install git with one of the two last options or add manually C:\Program Files\Git\cmd to your PATH.
I'm on a vista laptop, trying out git for the first time.
I installed the msysgit version, and it installed a "git bash" shortcut on the desktop. When I run it, it seems to run in a cygwin kind of box, where C:\ is /c/
Is it safe to use git from the windows command line where /c/ is C:\? does that create any conflict with the way git expects the pathes to be like?
What about, if I init from the bash/cygwin console, then commit from the windows console? Does that create any trouble?
Note: Keep in mind that git does not track where the repository is at -- just references. In other words you can cleanly move an entire git directory (.git + working tree) and it still works fine.
It should work in either case assuming your environment variables allow you to run git from the windows command line.
Both point to the same actual directories (although referenced differently), and use the same executable to modify the repository.
When you install MSYS Git, it will give you 3 options related to system paths. Which one you choose will determine how you can use it. It sounds like you want the 3rd option, "Run Git and included tools from the windows command prompt". This will put all of the git-related binaries in the system path, allowing you to use git from a normal command prompt. Be aware that it also overrides a few built-in windows tools, as the warning in the installer says.
After installing msysgit, you should be able to right click on an empty folder and see options "Git GUI here" and "Git BASH here". If you click Git GUI here it will open a GUI. Have fun!