I usually do a
find with an environment variable as the path when searching for source code. Recently I replaced my environment variable with a symbolic link, and it broke Bash's shell completion. When I do a
find using the symlink it doesn't work, but if I use the actual path that the symlink points to, it works find.
ln -s /some/source/dir /the/source export SYMLINK=/the/source export DIR=/some/source/dir find $SYMLINK -name file.c // doesn't find anything find $DIR -name file.c // works as expected
In this example $SYMLINK is a symbolic link for $DIR's value.
So, why does bash handle symlink environment variables differently?