Opening xplr inside symlink changes to physical path

[MithicSpirit]

If I open xplr inside a directory that is a symlink, like /lib on most Linux systems, xplr will instead open in the corresponding physical path (/usr/lib in the previous example). Opening a subdirectory of a symlink also has the same behavior (/lib/gcc will open in /usr/lib/gcc).
The weirdest part about this is that xplr does support opening symlinks, for example by opening / in xplr then pressing l on /lib will make the path /lib instead of /usr/lib.

[sayanarijit]

If I open xplr inside a directory that is a symlink, like /lib on most Linux systems, xplr will instead open in the corresponding physical path (/usr/lib in the previous example). Opening a subdirectory of a symlink also has the same behavior (/lib/gcc will open in /usr/lib/gcc).

Thanks for reporting. We may be able to fix this.

The weirdest part about this is that xplr does support opening symlinks, for example by opening / in xplr then pressing l on /lib will make the path /lib instead of /usr/lib.

Yes... This was fixed in this pr. And this pr added support for following the actual path of the symlink.

[sayanarijit]

I was able to make xplr $PWD work. But, plain xplr still resolves the symlink.