ForkLift's Symbolic Link Handling - Relative vs Absolute

[pixelchutes]

I have really enjoyed using ForkLift over the past year, it has definitely become a tool I depend on daily when developing on my Mac.

Each day I connect to Linux servers for various SCP/FTPS purposes and there is only one annoying side effect I deal with daily when using ForkLift, and that is in regards to Symbolic Links.

When I access a symbolic link from shell, my location is always relative to previous location, where the "parent" directory is the source location containing the reference to the symbolic link. This is also the behavior in WinSCP application on Windows. In ForkLift, however, when I access a symbolic link, the path changes to absolute path of symbolic link, preventing quick navigation into and back out of a symbolically linked location.

For Example:

/path/to/files may contain a symlink to shared location (such as: /extra/more_files) with a similar name, say "more_files"

Example symlink: /path/to/files/more_files => /extra/more_files

When in ForkLift, it would be nice to be in /path/to/files, browse into "more_files" (aka /extra/more_files), and have the Back button take you back to "/path/to/files", opposed to "/extra" how it currently operates today.

Perhaps my perspective on the matter is a bit skewed, which is why ForkLift's Symbolic Link handling may benefit from a new Preference/Option that gives the USER a choice over how to handle navigation of symbolic link: Absolute or Relative

[Debora68]

I think a graphic, symbolic representation of the work performed, or to be performed, on a product as it passes through some or all of the stages in the process.