It is better to have atleast some fall back capabilities(for searching across files, searching within files, sorting etc) build in.
It is better to have atleast some fall back capabilities(for searching across files, searching within files, sorting etc) build in.
The author likely has git, which provides a userland. And she/he is talking about gvim.exe, so is not restricted in what she/he can choose to install, and by now, might be using nvim-qt.exe.
Edit: just realized it always posed itself as a “building platform”, lol. It really is a full-blown GNU system that works on windows. As in GNU/Linux, but there’s no linux kernel. All the /usr/bin tools are there, including pacman as a package manager (from Arch). You can install virtually everything from there.
Notwithstanding that the third party userland is possibly not necessarily, since the windows userland most likely has all the features needed for Vim to make these functionalities work.
Since the editor is intended to be a multi-plaform product, it is better if atleast a windows userland based mechanism could be provided on windows platform, if the mechanisms could not be achieved through an inbuilt platform-agnostic manner.
What if you need a "portable" ( in the windows sense of the term, it means that the program can be used without need for an installation process) version of the editor?
I think it all is a huge time sink on the end user, who would instead get some usefull progress done on their projects.
May because WSL becomes a huge dependency and many windows boxes don't have it installed, whereas windows userland is always available.
At work, though, I've been doing dev work primarily in Windows for over a decade.
Never needed WSL.
(Maybe because I use Emacs? I dunno)