mwendt

If you have used the file transfer (SFTP) function in an SSH terminal and then disable it by clicking the button in the header of the SSH terminal again, the transfer status table remains at the bottom of the SSH terminal and cannot be closed.

Hello,

Thank you for the request, I think it would be an interesting addition. Out of curiosity, have you used a different SFTP client that also supports this? I'm asking as maybe we could take inspiration from their workflow.

Regards,

@Hubert Mireault

Mr Mireault,

Once again, my answer to your question is: have a look at WinSCP ;-)

When it comes to FTP/SFTP/SCP, this software has been and remains one of the most widely used on Windows.

Hallo,

yes, there are bookmarks for the remote site.

But why aren’t there any for the local directories?

Incidentally, the ‘local’ bookmarks shouldn’t be tied to the SSH terminal either, but should be available across the board...

Typically, the same directories are often used for SFTP transfers (this applies to both the host and the client). It would therefore be extremely useful if you could define 3, 5 or 10 favourite directories for each side, thereby enabling you to work much more quickly.

When you use the ‘Refresh Directory’ button during an SFTP transfer in an SSH session, you end up back at the top-level directory and then have to laboriously navigate back down to the nth subdirectory (the one you were already in).

Instead, you should remain in the current directory when refreshing.

If someone tries to copy data from their local machine to the SSH host using drag and drop, no error message appears if the permissions do not allow it. A message would be helpful in this case.

The built-in SFTP for SSH sessions is useful. However, there is no way to distinguish between binary and text files. In particular, I really miss the automatic conversion of line breaks when transferring text files between Unix and Windows (take a look at WinSCP ;-)