Closed GoogleCodeExporter closed 8 years ago
1.4.0.4's file transfer has a new pane which has a local browser where you can
drop files onto.
I might try to allow remote-to-explorer drag and drop later, but it's a bit
involved.
http://blogs.msdn.com/b/delay/archive/2009/10/26/creating-something-from-nothing
-developer-friendly-virtual-file-implementation-for-net.aspx
Original comment by btatey...@gmail.com
on 22 May 2013 at 5:13
Original comment by btatey...@gmail.com
on 22 May 2013 at 5:22
in remote machine by default it is trying to open /home/<loginuser> directory.
In case if in remote machine directory does not exist then it throws error as
below
2014-01-16 10:03:44,900 INFO PscpClient - Process exited, pid=7880,
exitCode=0
2014-01-16 10:03:44,902 ERROR BrowserPresenter - Unable to open /home/root:
no such file or directory
2014-01-16 10:04:35,327 DEBUG SuperPuTTY - STATUS: Editing Options
This should be configurable i.e. which directory i want to list for PscpClient
process
Original comment by singhi...@gmail.com
on 16 Jan 2014 at 4:43
The root user is a typical example, as there is no /home/root. As a workaround,
I added asymlink (cd /home && ln -s /root/) and the file transfer pane works
fine.
Original comment by stoumpos...@gmail.com
on 24 Mar 2014 at 11:41
Please fix the issue. On most servers I handle the expectation of /home/$user
to exist is simply wrong, so the file transfer feature is useless. While a
configurable as fix would be the best solution IMO, a quick fix would be to
fall back to / if /home/$user can't be found.
Original comment by noack.mi...@googlemail.com
on 6 Mar 2015 at 10:38
Original issue reported on code.google.com by
anthony....@gmail.com
on 13 Mar 2013 at 5:12