vim wrote:- will be nice to have 'open in browser' with the real url, is it possible at all?
vim wrote:- maybe creating a sublime-project automatically to cover the remote directory, is it possible at all? (i.e. remote list of the whole directory tree)?
vim wrote:- possible bug? somehow, with some filenames and directories i get a leading space before their name, which prevent from successfully opening it.
no, i was thinking of the http address, but maybe i am way off here (to open html pages on the site)gpfsmurf wrote:vim wrote:- will be nice to have 'open in browser' with the real url, is it possible at all?
It's possible to have something like "ftp://hostname/remotedir/filename", is that what you want?
gpfsmurf wrote:Yes its probably a bug. The filenames are parsed from the ftp LIST command, which has a different output on each kind of FTP server, so the parsing is not perfect. It's done by grizzled/net/ftp/parse.py, which i've already modified to work with newer FTP servers.
To fix it, I need something from you:
- in a CMD window, run c:\program files\winscp\winscp.com (.com, not .exe)
- type "open mysessionname" where mysessionname is the name that you see in the WinSCP stored sessions
- type "cd thedir" where thedir is a dir that has files with problems
- type "ls", which will send a "list" command
- send me the output (specifically the lines of some file/dirs that have the problem)
- type 'exit' to close the session and quit
vim wrote:no, i was thinking of the http address, but maybe i am way off here (to open html pages on the site)
gpfsmurf wrote:I fixed the bug, update to the tip to get the latest changes
Users browsing this forum: Google [Bot] and 6 guests