Describe the bug
Trying to refresh a directory listing in tree view causes a second netrw to open in the window of previous buffer
To Reproduce
Detailed steps to reproduce the behavior:
vim -u .vimrc testfile using this vimrc:set nocp
let g:netrw_liststyle = 3
:Lexplore<c-l> to refresh the directory listingExpected behavior
Per the netrw-refresh documentation, <c-l> should refresh the directory listing in the current window.
Environment
β
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.![]()
Hi @smoogan, I just stumbled onto this as I was setting up my netrw and I'm seeing the same behaviour, and I'm also thinking I'd like the new listing to be displayed in the current window instead of a new one.
Have you found any workaround for this?
@k-takata have you got any idea what we could do here? I couldn't find anything in the docs.
You could try the latest development version from dr. Chip, available here: http://www.drchip.org/astronaut/vim/index.html#NETRW
ping @cecamp
Hi @chrisbra, thanks for that π I installed this and I just tried vanilla configuration, and dr. Chip options without luck so far, <ctrl+L> still refreshes the directory listing, I'm still looking into the help section.
still the same with netrw v171 and vim 9.0.749 :/
β
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Well, I just don't see anything wrong. I used the following file:
set nocp set hidden let g:netrw_liststyle= 3 let g:netrw_maxfilenamelen= 40 so $HOME/.vim/plugin/netrwPlugin.vim
and used vim -u lexpl.vimrc somefile, then :Lexplore. Pressing ctrl-l did not affect the display.
β
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
This issue still persists, only in tree mode. Are there no patches for these yet?
β
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Can you help to reproduce this with some simple steps to help getting this fixed?
β
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
@chrisbra I am not sure why this issue is being triggered, so unfortunately, I won't be able to share a way to reproduce this issue. However, I can share the log files.
β
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
can you not provide steps you do to reproduce this?
β
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Here's the following step, along with a screencast @chrisbra :
cd to a project directory and open vim:LexploretestScreencast from 2023-06-15 13-25-41.webm
β
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
Note: Step 3 is not necessary, it is however necessary to be in Tree-View-mode.
i three times to cycle to tree viewβ
Reply to this email directly, view it on GitHub.
You are receiving this because you are subscribed to this thread.![]()
--
--
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
---
You received this message because you are subscribed to the Google Groups "vim_dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to vim_dev+u...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/vim_dev/vim/vim/issues/5964/1592588429%40github.com.
β
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.![]()
You could try the in-development version of netrw .
β
Reply to this email directly, view it on GitHub.
You are receiving this because you commented.![]()
@cecamp There's still no changes in the behaviour after installing the new vba plugin file.
Screencast from 2023-06-16 03-01-32.webm
β
Reply to this email directly, view it on GitHub.
You are receiving this because you commented.![]()