in reply to Re^4: Getting the absolute path of a script, without PWD (bug?)(update)
in thread Getting the shell's version of working directory, without PWD's help

> The question is why is bash's pwd defaulting differently inside Perl?

From qx

Similarly to system, if the string contains no shell metacharacters then it will executed directly.

Not sure what is included into "shell metacharacters" but a simple semicolon seems to suffice to force execution via the shell ...

lanx@ubuntu14-large:/tmp/sym$ perl -MCwd -E'say `pwd;` '
/tmp/sym

lanx@ubuntu14-large:/tmp/sym$ perl -MCwd -E'say `pwd` '
/tmp/dir

lanx@ubuntu14-large:/tmp/sym$

[download]

update

simplified code

Cheers Rolf
(addicted to the Perl Programming Language :)
Wikisyntax for the Monastery

Replies are listed 'Best First'.
Re^6: Getting the absolute path of a script, without PWD (bug)
by perlancar (Hermit) on Jul 16, 2021 at 07:52 UTC
    You're 1 minute faster :-)
[reply]
      Please, you should really file a bugreport against Cwd.

      Maybe they can't fix cwd() b/c of backwards compatibility but should at least clarify the documentation.

      From my POV it's already silly to call two different routines getcwd() and cwd()

      So you could suggest to add a new pwd() which always does something like `pwd -L`

      Cheers Rolf
      (addicted to the Perl Programming Language :)
      Wikisyntax for the Monastery

[reply]
[d/l]
[select]
        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`.
[reply]

In Section Seekers of Perl Wisdom