Skip to content
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

Use current script execution path to get relative path #1

Merged
merged 2 commits into from
Jul 11, 2018

Conversation

apm963
Copy link
Contributor

@apm963 apm963 commented Jul 11, 2018

When running in my current environment (git bash for Windows) the script
was failing with the following message:

$ ges
/c/Users/user-name/git/github/git-extra-status/bin/ges: line 1: 
../src/git-extra-status.sh: No such file or directory

This was because the relative path in the running script was being
inherited from the shell's pwd, not of the script itself.

I also added something to proxy, or forward, args from a executed bin script to the src shell scripts. Without this, I was unable to run ges * or ges repo-name or anything other than ges since the args were being dropped.

When running in my current environment (git bash for Windows) the script 
was failing with the following message:
```sh
$ ges
/c/Users/user-name/git/github/git-extra-status/bin/ges: line 1: 
../src/git-extra-status.sh: No such file or directory
```
This was because the relative path in the running script was being 
inherited from the shell's pwd, not of the script itself.
Without this, running `ges` with a dir name(s) as args would not be able 
to be read by the .sh scripts and would cause the command to silently 
fail
@sandeep1995 sandeep1995 merged commit 6dd12a5 into sandeep1995:develop Jul 11, 2018
@apm963 apm963 deleted the develop branch July 11, 2018 17:18
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants