Differences
This shows you the differences between the selected revisions of the page.
| ui_login_directories 2017-02-02 | ui_login_directories 2023-05-24 (current) | ||
| Line 1: | Line 1: | ||
| - | ====== Directories Page (Advanced Site Settings dialog) ====== | + | ====== The Directories Page (Advanced Site Settings dialog) ====== |
| The //Directories page// on the [[ui_login_advanced|Advanced Site Settings dialog]] allows user to configure initial session directories and the way how directory content is read. | The //Directories page// on the [[ui_login_advanced|Advanced Site Settings dialog]] allows user to configure initial session directories and the way how directory content is read. | ||
| Line 13: | Line 13: | ||
| The //Remote directory// box defines the initial remote directory opened in panel. When //Remember last used directory// is ticked the path is updated whenever the session is closed. When the initial directory is not specified the user home directory is usually opened on startup. Note that this may not be true particularly for SFTP servers. | The //Remote directory// box defines the initial remote directory opened in panel. When //Remember last used directory// is ticked the path is updated whenever the session is closed. When the initial directory is not specified the user home directory is usually opened on startup. Note that this may not be true particularly for SFTP servers. | ||
| - | The //Local directory// box defines the initial local directory opened in local panel on [[interfaces|Commander interface]]. The path is not used with [[interfaces|Explorer interface]]. When the initial directory is not specified the local user //My Documents// folder is used. | + | The //Local directory// box defines the initial [[local_path|local directory]] opened in local panel on [[interfaces|Commander interface]]. The path is not used with [[interfaces|Explorer interface]]. When the initial directory is not specified the local user //My Documents// folder is used. |
| The initial directories also define home directories (for //Go To > Home Directory// command) when //[[ui_pref_panels#common|Default directory is home directory]]// preference option is enabled and //Remember last used directory// session option (see above) is disabled. | The initial directories also define home directories (for //Go To > Home Directory// command) when //[[ui_pref_panels#common|Default directory is home directory]]// preference option is enabled and //Remember last used directory// session option (see above) is disabled. | ||
| 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 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. | + | 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]] and [[S3]] protocols.)) 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. | + | 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]] and [[S3]] protocols. |
| ===== Further Reading ===== | ===== Further Reading ===== | ||
| Read more about [[ui_login|Login dialog]] and [[ui_login_advanced|Advanced Site Settings dialog]]. | Read more about [[ui_login|Login dialog]] and [[ui_login_advanced|Advanced Site Settings dialog]]. | ||