![]() It is because etc\profile.d\git-prompt.sh does not check the shell before including git-completion. If [ "x $ " #if you have problems with your path, just print it somewhere #echo "PATH set to" > ~/.shelllog #echo $PATH | /usr/bin/sed 's/^\|:/\n /g'> ~/.shelllog export HISTSIZE=999999999ĮRROR: this script is obsolete, please see git-completion.zsh ![]() Please note the escape the backslash in the path. For me, the path for bash.exe is C:Program FilesGitbinbash.exe, so the key-value looks like this. ![]() # ~/.zshenv # This is the first file that zsh is loading # my preferred locale/lang settings export LC_ALL=C.utf8 name: Git-Bash Configure Bash Path: In the commandline key, we will provide the path of bash.exe. You can now pass any arguments you want and run the script: Alright, this brings us. To see these special variables in action take a look at the following variables.sh bash script: /bin/bash echo 'Name of the script: 0' echo 'Total number of arguments: ' echo 'Values of all the arguments: '. # wl at DESKTOP-EJL17NS in /c/work/project on git:master The process id of the last executed command. ![]() Looks like it is slightly faster, but anyway, 2 seconds, if not in git repo, and 5-7 seconds in a small repo. cat -e dosfile.sh /bin/bashM This is a fileM M M M M echo 'yay i ran'M A word of advice The problems with CR characters causing issues is not only limited to scripts either, I have seen many problems where a configuration file was not read properly because the file contained DOS style EOL characters.
0 Comments
Leave a Reply. |