Hi, If you don't mind trying software at very early stages of the development, you can try Cheetah. Pre-compiled, unofficial, not- reviewed version is available at:
http://kirill.ca/public/cheetah-080209.zip It's basically an Explorer extension that adds two menu items: - Git Gui with context-sensitive name; - Git Bash Here that behaves as you requested (I believe). To install: - install Git first; - copy git_shell_ext.dll somewhere closer to git.exe (same folder might work); - execute "regsvr32 git_shell_ext.dll" from a command prompt. If you want to install machine-wide, and not only for the current user, you can use "regsvr32 -n -i:machine git_shell_ext.dll". After that you should see two extra items in a context menu of each file and folder (including the background of a folder). If you don't see them, please, verify that you have: [HKEY_CURRENT_USER\Software\Git-Cheetah] PathToMsys=c:\\msysgit In reality, if you copied the extension to the same folder as git.exe, you'll likely see PathToMsys=c:\msysgit\bin\.. It's probably best to unregister shell extensions, installed by Git installer, otherwise you may have hard time to distinguish between Git Bash Here and Git Bash Here :) Dscho, what a perfect timing ;) Thanks! You're great! -- Kirill. On Feb 9, 1:12 pm, Stephan Hennig <[EMAIL PROTECTED]> wrote: > A common use-case for me is to open a Git bash in a WC directory and > have Explorer showing the same directory in parallel. Currently, this > requires me to > > 1. navigate to the parent directory of the WC, > 2. right-click on the WC directory and click 'Open Bash Here', > 3. move the Git console out of the way, > 4. enter the WC directory in Explorer, > 5. activate Git bash. > > A much more pleasant behaviour (for me) would be to navigate to the > target WC directory and open a Git bash after arriving there. That > would merge operations 1 and 4 and save me from doing operations > 3 and 5.
