Tuesday, January 14, 2014

Re: problems (and bugs) with netrw

> Just tried this sequence out and didn't see any problem. Please try the
> latest version of netrw (v150t, available from my website:
>
> http://www.drchip.org/astronaut/vim/index.html#NETRW)

I installed it. if there's nothing else to do to load the new version then the problem still happens. it might be some interactions with other plugin, but i've no idea how to find out.

I see that the second time i open the help ":echo &ft" outputs "text", but I have no idea why it happens

http://www.freeimagehosting.net/ksvo8



> I haven't seen this one, please let me know if you get a way to
> reproduce it (please use v150t, though).

currently it hasn't happened yet. as I said it was random, but it seemed to happen quite frequently, so the fact that i haven't seen it yet might mean it's solved... anyway, if it happens again i'll report it, thanks :)



> > and now for the problem: when i open netrw, i don't know how to go back to the file i was editing... I mean, I don't want to select a file and open it, I want to close netrw and go back to whatever i was editing before.
>
> :Rexplore

i suppose I didn't explain the problem correctly. I don't want to go back to netrw, I want to close netrw and go back to the file I was editing (I'm opening it in the current window, not in another split)



> Netrw v150t's cursor was on the ".." after moving up a directory. Please
> try v150t. I didn't see a blank line with g:netrw_banner= 0, either.

i still do

http://www.freeimagehosting.net/ua5m1

thanks for the help

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

---
You received this message because you are subscribed to the Google Groups "vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_use+unsubscribe@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.

No comments:

Post a Comment