Re: netrw and symbolic links

Tony Mechelynck wrote:
> On 07/10/10 03:39, Charles E Campbell Jr wrote:
>> ...snipped...
>>
>> Remote directories are probed with directory listing commands; remote
>> files are downloaded and made available for local editing, so clearly
>> these two operations are quite different. Netrw chooses to treat things
>> as files unless there's a trailing "/", which, for symbolically linked
>> directories, isn't there, so netrw ends up treating symbolically linked
>> directories as files.
>>
>> One idea would be to always try to change directory and to intercept the
>> occasional error to require treating it as a file. Unfortunately this
>> means that several transfer requests are being made, which in turn means
>> multiple requests for passwords -- which I'm trying to minimize.
>>
> Multiple requests (to the user) for passwords won't happen if the
> symlink points to a file or directory on the same server, which is
> usually the case, see ":help netrw-login".
Netrw doesn't hold the connection open; each transfer is independent.
So, if netrw did the "always try to change directory" approach:

assume the "word" being clicked upon is a symbolic link to a file.
Netrw attempts to change directory based on that word. (ftp operation
#1, requiring a password)
Netrw receives an error message (do all ftp clients/servers give the
same message? unfortunately, not likely).
Netrw then attempts to get the "word" as a file (ftp operation #2,
requiring a password).

I'm thinking about making a map, gd, which would force treatment of the
word under the cursor as a directory.

Regards,
Chip Campbell

--
You received this message from the "vim_use" maillist.
Do not top-post! Type your reply below the text you are replying to.
For more information, visit http://www.vim.org/maillist.php