Symbolic links are also easy to spot. Using ls -l, you can see which files are
symbolic links and where they point to.
> ls -l /
-rwxrwxr-t 1 root admin 9 Nov 28 18:49 mach -> /mach.sym
-r--r--r-- 1 root admin 705904 Nov 28 18:49 mach.sym
-rw-r--r-- 1 root wheel 3728752 Nov 5 23:01 mach_kernel
drwxr-xr-x 3 chrisc admin 102 Nov 13 22:33 opt
drwxr-xr-x 6 root wheel 204 Nov 28 18:49 private
drwxr-xr-x 60 root wheel 2040 Nov 28 18:43 sbin
lrwxrwxr-t 1 root admin 11 Nov 28 18:49 tmp -> private/tmp
drwxr-xr-x 12 root wheel 408 Jul 14 00:21 usr
lrwxrwxr-t 1 root admin 11 Nov 28 18:49 var -> private/var
(from : http://ezine.daemonnews.org/200212/symlink.html)
With a simple ls command, the symlinks will appear as directories, which
explains why pspad is confused.
What we would expect it to do is open the directory the symlink points to.
In the example I gave, "tmp" and "var" both have the setting "l" at the
beginning of the line (where a directory has a "d", and a file has a "-").
In the case of symlinks, pspad needs to open the part located after the "->"
symbol.
Meaning, when we try to open "var", pspad will go and open "private/var".
These symlinks can point to relative OR absolute paths (I don't know whether it
has an impact on your ftp engine or not, but still I thought I would mention
it).
Hope it helps, and thank you for being reactive to suggestions.
--
<http://forum.pspad.com/read.php?2,38391,44984>
PSPad freeware editor http://www.pspad.com
