[EMAIL PROTECTED] schrieb: >> 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. > > at first I did not understand your problem at all, but then it came to > my mind that you're probably launching the "Git Bash Here" that comes > with the msysGit installer from the context menu that pops up when > right-clicking a directory in the *list view* of Windows Explorer.
Yes, that's the way I used to navigate in Explorer. Actually, I'm not using Windows Explorer, but a third party file browser (Idoswin Free, <URL:http://www.idoswin.de/>). In list view this browser inserts .. in front of directories and files indicating the parent directory. This makes navigating in deeply nested directories convenient; going three or five directory levels up requires just clicking several times /at the same location/ (and also with less mouse movement than via the 'Up' button in explorer). Though, I prefer Idoswin over Explorer for other reasons and never noticed this difference before. > I usually have the same workflow as you, and what I do is to select > the WC directory I'm interested in in the *tree view*, use the "Git > Bash Here" from there, and I'm set. Navigating in tree view is not half as convenient, IMHO. All directories constantly change position depending on how many sub-directories are currently open, resulting in too much scrolling for me. I don't want to say one of the variants is better, but navigating in list view just fits better for me. As for msysGit, I think it shouldn't prefer one behaviour over the other. Both, navigating in list and tree view, should be equally convenient. As I proposed in my previous mail, changing the behaviour of 'Git bash here' and introducing a dynamic menu 'Git bash in xxx' would serve both types of users. If the Installer can't handle dynamic menus, I propose to bundle Cheetah with msysGit. But then, please add means to activate and deactivate /any/ menu entries individually (clone etc.) Best regards, Stephan Hennig
