gsp ?? TTTTTT BBBBBBBBB ?? a b/ ?? "a\"b/" ?? a$b/ ?? a&b/ ?? a'b/ ?? ab/ ?? "a\303\251/" ?? brackets/ ?? ext/ ?? t ?? tttt aaaa init TTTTTT BBBBBBBBB a b/ a"b/ a/ a&b/ a'b/ ab/ aé/ brackets/ ext/ t tttt aaaa /…test/fixtures/_filedir> gsp A "TTTTTT BBBBBBBBB" A "a b/i" A "a\"b/d" A a$b/h A a&b/f A a'b/c A ab/e A "a\303\251/g" A brackets/[x] A brackets/x A ext/ee.e1 A ext/ff.e2 A ext/foo/.gitignore A ext/gg.e1 A ext/hh.e2 A ext/ii.E1 A t A "tttt aaaa" init TTTTTT BBBBBBBBB a b/ a"b/ amaster/ a&b/ a'b/ ab/ aé/ brackets/ ext/ t tttt aaaa /…test/fixtures/_filedir>
…age from appearing in the prompt when $git_dir includes space character(s) For example, assume a git repository located at /Volumes/Macintosh HD/Users/tom/src/myrepository: - this bug does not appear when the working directory is the root of the git repository ( e.g. /Volumes/Macintosh HD/Users/tom/src/myrepository ), as $git_dir returns ".git" - the bug only appears if the directory is changed to one other than the root of the repository ( e.g. /Volumes/Macintosh HD/Users/tom/src/myrepository/DIRECTORY ), as $git_dir will then return the full path "/Volumes/Macintosh HD/Users/tom/src/myrepository/.git". The space between "Macintosh" and "HD" will cause 'grep "^ref:" $git_dir/HEAD' to fail. Adding quotation marks around $git_dir/HEAD allows the grep test to succeed, even when the path includes space character(s).
I do not understand what it does. From Issue 15: Also, in exploring this problem I noticed that disable_set_shell_label doesn't work correctly for me. I fixed this problem by declaring disable_set_shell_label and enable_set_shell_label to have the "trace" attribute in bash. This is done by adding: declare -ft disable_set_shell_label and declare -ft enable_set_shell_label after the definitions of those functions in git-prompt.sh.