query: Bash script - trying to get path of script
positive_passages.docid: 4162
positive_passages.text: How can I get the source directory of a Bash script from within the script itself?
negative_passages.docid: 76632
negative_passages.text: How can you quickly get the complete path to a file for use in terminal?
negative_passages.docid: 17691
negative_passages.text: Determine path of the executing script
negative_passages.docid: 43922
negative_passages.text: How can I find the path for an executable?
negative_passages.docid: 7715
negative_passages.text: Get path to application?
negative_passages.docid: 41578
negative_passages.text: How to iterate over arguments in a Bash script
negative_passages.docid: 85461
negative_passages.text: Passing arguments to a script
negative_passages.docid: 27806
negative_passages.text: Redirect a portion of a bash script to a file to capture set -x output
negative_passages.docid: 126609
negative_passages.text: What is the difference between running "bash script.sh" and "./script.sh"?
negative_passages.docid: 118409
negative_passages.text: storing a directory name with spaces in a bash variable
negative_passages.docid: 28904
negative_passages.text: Bash script returning "Not found" error
negative_passages.docid: 87102
negative_passages.text: How to get script directory in POSIX sh?
negative_passages.docid: 154472
negative_passages.text: Can I export a variable to the environment from a bash script without sourcing it?
negative_passages.docid: 82805
negative_passages.text: How to get the location of a program in Ubuntu terminal?
negative_passages.docid: 72828
negative_passages.text: Analogue of NotebookDirectory[] for scripts (to get the directory path of my script.m)?
negative_passages.docid: 25487
negative_passages.text: How to store a command in a variable in a shell script?
negative_passages.docid: 69145
negative_passages.text: Why do you need ./ (dot-slash) before executable or script name to run it in bash?