Russ SharekAfter years of running `ls` commands to figure out where a symlink was pointing, today I found out about the readlink1 command:
a spoon full of cheese@RussSharek tbh, I still run
ls, because that's shorter, and most of the time I don't want to pipe the output elsewhere anyway.I'll likely do the same. In this case, I needed the output for a script so the tool was really handy.