Is your feature request about something that is currently impossible or hard to do? Please describe the problem.
Currently, netrw comes out of the box in vim as a file-explorer (among other things) but there are quite a few issues with it and attempts have been made to mitigate it.
Vim-dirvish is a similar plugin with less code but much more reliability than netrw. It would be nice if this plugin is integrated into vanilla vim instead of netrw.
Describe the solution you'd like
Switching to vim-dirvish as the default file explorer in vim.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
I've been using Dirvish pretty much since the day it came out, but swapping out Netrw with Dirvish means people using (and expecting) Netrw now will suddenly be presented with Dirvish. It will also break custom mappings, commands, and whatnot people have for Netrw.
I really like Vim for its stability; you can take a vimrc from 20 years ago and most likely everything will still work. It's one of Vim's best features that is probably not mentioned often enough.
So I don't think this is a good idea. Even Neovim – which tends to be a little bit more relaxed about compatibility – retains Netrw for presumably the same reason (and the author of Dirvish is one of the core Neovim contributors).
I really like Vim for its stability; you can take a vimrc from 20 years ago and most likely everything will still work.
It has become worse with the advent of package managers though (I stopped using Vim as my default IDE shortly before the Great Schism of Package Managers™).
Netrw does so much more than Dirvish…
Is this a joke?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Triage notifications on the go with GitHub Mobile for iOS or Android.
... swapping out Netrw with Dirvish means people using (and expecting) Netrw now will suddenly be presented with Dirvish.
I wouldn't say "suddenly".. people will need to explicitly update Vim and it would be beneficial to update to modern Vim with modern plugins IMO. And people wishing use existing setup don't need to do anything - don't need to update vim or do anything. Only the ones who update (vim or distribution) will notice any change, which is somewhat expected I would say.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Why not fix the issues with netrw instead of switching to something entirely different?
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
There is also this issue that @brammool opened a while ago:
Help wanted: netrw maintenance #4663
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub, or unsubscribe.
Git is a good example of a tool that is just too complicated for casual use.
Which is another reason why I find it sad that the reference Vim repository is hosted here, to be honest.
—
You are receiving this because you are subscribed to this thread.
Reply to this email directly, view it on GitHub.
—
You are receiving this because you are subscribed to this thread.