csonto/bash-completion
1
0
Fork 0
Code Issues Pull Requests Packages Projects Releases Wiki Activity

Fix running test scripts without giving a path to them.

Browse Source 
For example "cd test ; bash runCompletion [...]".
This commit is contained in:
Ville Skyttä 2010-04-21 23:19:34 +03:00
parent a7cd88bb67
commit f9f49786ca
3 changed files with 3 additions and 3 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

2
test/run
View File

@ -31,7 +31,7 @@ set_tool() {
} }
cd "${BASH_SOURCE[0]%/*}" cd "$(dirname "${BASH_SOURCE[0]}")"
# Loop over the arguments. # Loop over the arguments.

2
test/runCompletion
View File

@ -4,4 +4,4 @@
# isn't initialized at that point (i.e. output of `expect' is shown on # isn't initialized at that point (i.e. output of `expect' is shown on
# stdout - `open_logs' hasn't run yet?). And running code from a library # stdout - `open_logs' hasn't run yet?). And running code from a library
# file isn't probably a good idea either. # file isn't probably a good idea either.
"$BASH" "${BASH_SOURCE[0]%/*}/run" --tool completion $* "$BASH" "$(dirname "${BASH_SOURCE[0]}")/run" --tool completion $*

2
test/runUnit
View File

@ -4,4 +4,4 @@
# isn't initialized at that point (i.e. output of `expect' is shown on # isn't initialized at that point (i.e. output of `expect' is shown on
# stdout - `open_logs' hasn't run yet?). And running code from a library # stdout - `open_logs' hasn't run yet?). And running code from a library
# file isn't probably a good idea either. # file isn't probably a good idea either.
"$BASH" "${BASH_SOURCE[0]%/*}/run" --tool unit $* "$BASH" "$(dirname "${BASH_SOURCE[0]}")/run" --tool unit $*