I have a script that compares two unique directories for common file variables/attributes. The script is executed as follows:
script_cmp.ksh <reference_path> <target_path>

If the user uses the full path for the <target_path> argument, the script works correctly and displays the information (validated previously during development). If I allow the user to either pass in a '.' (for PWD) or leave the 2nd argument empty (assuming PWD), the data that is returned is incorrect compared to the known and validated good data.

Is there an unknown 'gotcha' I need to be aware of with regards to expanding the '.' in a script? Thanks!

I believe you can use the BASH_SOURCE variable within bash scripts to get this info, but not sure if it will work within korn shell.

http://www.gnu.org/software/bash/man...Variables.html

It might help if you posted some, you know, actual code. Then we might be able to spot the error.

Also, be aware that "." and ".." are not aliases or shortcuts or anything. They are real directory names, produced by the underlying filesystem to point to the current and parent directories. The shell you use has nothing to do with their definition, and should generally handle them just like any other path name, although it may be configured to treat them specially in some circumstances (ignoring them in globs, for example).

I don't understand how this relates to the OP's question. On my system, "FUNCNAME" is empty, but pwd and "." (meaning "current directory") still works.

For the OP:
In normal ksh file operations, does "." work to signify current directory? If so, then you may need to use quotes somewhere to keep it from being seen as a regex meaning "any character".