it took me few times to understand anytime i need WinSCP i just have to press F12.

few comments:- will be nice to have 'open in browser' with the real url, is it possible at all?- 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)?- possible bug? somehow, with some filenames and directories i get a leading space before their name, which prevent from successfully opening it.

vim wrote:- possible bug? somehow, with some filenames and directories i get a leading space before their name, which prevent from successfully opening it.

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:- 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?

no, i was thinking of the http address, but maybe i am way off here (to open html pages on the site)

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

1. implementing recursive ls, which will run in the background upon connection and will list all files. once it done the result will be cached for the session. and if new files are created with sublime on remote locaion, those can be added to the list. the list can be updated asynchronously if the user already tries to use this (sublime support it).

2. use plink (installed with putty) to execute remote commands, so the 'find' command could be used to map the whole tree of files, and like (1) the result can be cached.

vim wrote:no, i was thinking of the http address, but maybe i am way off here (to open html pages on the site)

Well if there's a deterministic rule to create the URL then yeah... We have the FTP hostname, remote dir, and filename to work with.Something like this: http://hostname/directory/filenamewhere the directory can be a subdirectory of the remote dir (anything under '.....htdocs/' or '.....www/', for instance)

getting the directory tree via putty/find would be quite fast, but it won't work with ftp-only servers ( sadly, some people still have to work that way ).

for an universal solution, the recursive listing via winscp would be the way to go (works with ftp), but it's slow on deep trees.

maybe asynchronously building of the directory-tree and using some kind of intelligent cache like you mentionend, would hide the slowness of that approach from the user (at least caching will, after the initial directory-tree is build).