-
Notifications
You must be signed in to change notification settings - Fork 2.7k
Git Bash: Space in paths not handled properly #748
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Comments
I can reproduce the error by running |
I'm not able to reproduce this on Windows 7 Professional SP1 64-bit, and my PATH setting incudes lots of spaces, so there's definitely something weird going on here. On the assumption that it isn's simply a damaged Git for Windows installation, could you please try running the following from the Windows command prompt?
All this done is temporarily remove |
@lifenstein there is a clear indication of drush being installed. So you did not tell us the complete truth: you probably have installed Drupal in some form at some point, and it is quite possible that your |
@landstander668 I am having the issue at my work computer, will do as you say when I get back to work. @dscho Didn't realise Drush could be a factor! The issue seemed to be from the export commands somewhere in the init not handling spaces in paths correctly, and thought the PATH being too long may have had something to do with it. |
Well, it was in the log.
Probably missing quoting. |
The issue was fixed by removing reference to drush in bashrc. Thanks @dscho ! |
Thanks for reporting back! |
This feature was introduced in #736 but had a few pain points that were discovered when testing the full replacement of the existing post-index-change and post-command hooks in our internal environment: 1. When using `core.hooksPath` to point to a directory within the worktree, the sentinel files were being written into the worktree. Write to `$GITDIR/info/` instead. 2. The existing internal post-index-change hook only signaled that work needed to be done if actually the _worktree_ changed. Make the sentinel file logic more restrictive to only write in these cases. Tests are added to confirm both of these behavior changes. To reflect the changed behavior, the name `post-index-change` was renamed to `worktree-change`.
Uh oh!
There was an error while loading. Please reload this page.
or closed issue
matching what I'm seeing
Setup
Which version of Git for Windows are you using? 32-bit or 64-bit? Include the
output of
git version
as well.Git 2.8.2 64 bit
Which version of Windows are you running? 32-bit or 64-bit?
Windows 7 Enterprise, 64-bit, SP1
What options did you set as part of the installation? Or did you choose the
defaults?
Components: No "Additional icons"; checked everything else.
PATH: 'Use Git and optional Unix tools from the Windows Command Prompt'
SSH Executable: OpenSSH
Line Ending conversions: Checkout Windows-style, commit Unix-style line endings
Emulator: MinTTY
Extra Options: Both "Enable file system caching" and "Enable Git Credential Manager" checked.
Any other interesting things about your environment that might be related
to the issue you're seeing?
Details
Which terminal/shell are you running Git from? e.g Bash/CMD/PowerShell/other
Git Bash
What commands did you run to trigger this issue? If you can provide a
Minimal, Complete, and Verifiable example
this will help us understand the issue.
What did you expect to occur after running these commands?
What actually happened instead?
If the problem was occurring with a specific repository, can you provide the
URL to that repository to help us with testing?
(No.)
The text was updated successfully, but these errors were encountered: