Differences
This shows you the differences between the selected revisions of the page.
| 2016-03-16 | 2016-05-27 | ||
| 5.8.2 Bug 51 Option to follow or not follow symbolic links (martin) | preferring "symbolic/hard link" over "symlink/hardlink" (martin) | ||
| Line 24: | Line 24: | ||
| Note that when //Cache visited remote directories// is turned off, remote [[ui_file_panel|panel]] will not get refreshed after [[transfer_queue|background transfer]] completes. | Note that when //Cache visited remote directories// is turned off, remote [[ui_file_panel|panel]] will not get refreshed after [[transfer_queue|background transfer]] completes. | ||
| - | When WinSCP reads directory content, it by default also resolves any symbolic links (symlinks) it finds. Particularly to learn if they point to file or directory. If a directory contains too many symbolic links, it can slow down opening the directory. You may disable the feature by unticking //Resolve symbolic links// to speed it up. You may also use the option when WinSCP hangs when resolving cyclic links. While WinSCP detects most cyclic links, it can still hang when it encounters more complex symbolic link "systems". Note that when the resolving is disabled, creating links is effectively disabled too. Also when the resolving is disabled or not supported, double-clicking on any remote file will be interpreted as an attempt to open the directory with the same name.((Resolving symlinks is not supported with [[sftp|SFTP-2]] and older. It is also not supported with [[ftp|FTP]] protocol, but when double-clicking a file, WinSCP behaves as if it is. The option is further not available with [[WebDAV]] protocol.)) This allows opening links pointing to directories even when WinSCP does not know they are links. | + | When WinSCP reads directory content, it by default also resolves any symbolic links (symlinks) it finds. Particularly to learn if they point to file or directory. If a directory contains too many symbolic links, it can slow down opening the directory. You may disable the feature by unticking //Resolve symbolic links// to speed it up. You may also use the option when WinSCP hangs when resolving cyclic links. While WinSCP detects most cyclic links, it can still hang when it encounters more complex symbolic link "systems". Note that when the resolving is disabled, creating links is effectively disabled too. Also when the resolving is disabled or not supported, double-clicking on any remote file will be interpreted as an attempt to open the directory with the same name.((Resolving symbolic links is not supported with [[sftp|SFTP-2]] and older. It is also not supported with [[ftp|FTP]] protocol, but when double-clicking a file, WinSCP behaves as if it is. The option is further not available with [[WebDAV]] protocol.)) This allows opening links pointing to directories even when WinSCP does not know they are links. |
| Check the //Follow symbolic links to directories// to have WinSCP follow symbolic links to directories, when operating with remote files (e.g. while downloading or deleting). The option is not available with [[WebDAV]] protocol. &beta_feature | Check the //Follow symbolic links to directories// to have WinSCP follow symbolic links to directories, when operating with remote files (e.g. while downloading or deleting). The option is not available with [[WebDAV]] protocol. &beta_feature | ||