Charles Campbell wrote:
Benjamin R. Haskell wrote:
On Wed, 31 Aug 2011, Benjamin R. Haskell wrote:
On Tue, 30 Aug 2011, Guy Halford-Thompson wrote:
Is this something that is likely to get fixed?
Seems very likely to me. And probably soon, based on his usual
turnaround time.
As far as I can tell, the source of the issue is that
autoload/netrw.vim's s:NetrwBrowse calls:
(line 2439 in v141n):
sil call netrw#NetRead(2,s:method."://".s:user.s:machine."/".s:path)
Note the lack of any port numbers. When running my example (with
:443), the dirname variable in that section properly contains that
:443 and g:netrw_port is set to 443, but it's not being used.
The easiest fix would be to use something like:
let url = s:method."://".s:user.s:machine.(s:port ? ":".s:port :
"")."/".s:path
and replace the two occurrences around line 2439 of:
s:method."://".s:user.s:machine."/".s:path
with:
url
This worked for me, so, patch attached.
I'll look into it. Been busy lately....
The patch looks good, so I'll include it. The latest netrw is available
for testing (which incorporates that patch) is available at my website:
http://drchip.0sites.net/astronaut/vim/index.html#NETRW (v143h).
Regards,
Chip Campbell
--
You received this message from the "vim_dev" 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
