Maybe after I'm more knowledgeable about the actual differences between getcwd() and cwd(). Right now, it's not clear that cwd() should be "fixed". getcwd() tries to call getcwd(3) or reimplements it, while cwd() makes no such promise. And this statement is not strictly wrong: "For most systems it is identical to `pwd` (but without the trailing line terminator)." Though it might benefit the reader to be aware of the difference between pwd -P and pwd -L, and which one the reader is getting with `pwd`.