Images are reused AI-generated editorial illustrations, not documentary photographs or verified product screenshots.
The current directory in Bash determines how many relative paths resolve. Before reading a project file or running a script, inspect that directory explicitly rather than assuming it is the folder you last opened in a graphical file manager.
Inspect the current directory in Bash
Use pwd to print the current working directory. Bash can distinguish logical paths from physical paths involving symbolic links through supported options such as pwd -L and pwd -P. Select the interpretation that matters for the task and avoid exposing private path names in public logs.
Understand how relative paths resolve
A path such as ./notes.txt refers to the current directory. Running a script stored elsewhere does not automatically change that directory to the script's location. Quote paths containing spaces, and inspect a known file rather than assuming a successful script invocation proves its path assumptions.
Navigate deliberately and recheck
Use cd with an explicit intended directory, then run pwd again. Changing directories can fail, so check the result before continuing with dependent work. Keep introductory examples read-only; do not combine uncertain directory navigation with deletion or broad file modifications.
A practical checklist
- Print the directory before dependent work.
- Distinguish logical and physical paths if relevant.
- Quote paths containing spaces.
- Check whether cd succeeded.
- Keep initial checks read-only.
Worked example
Illustrative example: a script is stored in a tools folder but is invoked from a project folder. Its ./notes.txt reference resolves in the project folder. The user confirms this with pwd and a read-only file check rather than moving files until the script appears to work.
Common questions
Does running a script change directories automatically? No. Can PWD and a physical path differ around symlinks? Yes. Does an unsuccessful cd mean later commands use the requested directory? No; verify navigation before continuing.
What to do next
State the expected working directory in the script's usage notes. A clear path assumption is easier to maintain than an invisible dependency on a previous terminal command.