There’s a typo in the news title: it’s “poll”, not “pool”.
Neovim's Next Feature Poll
11–20 of 105 posts
Re: Neovim's Next Feature Poll
#12How could they make a sublime-style code minimap in a CLI app?
They are willing to make it more like gvim, running in a separate window, and one of targets of neovim is to use a modern graphics backend to achieve that.
Re: Neovim's Next Feature Poll
#13Loving the progress of Neovim so far, even better that notable plugin authors ( https://github.com/neovim/neovim/issues/622#issuecomment-415... ) are getting involved.
I've always wanted to write Vim plugins, but Vimscript and the RPC contortions always looked too hairy for me to get involved -- I'm excited for the new vim-embedding interface so I can get real VIM compatibility with my IDEs.
Re: Neovim's Next Feature Poll
#14If that's not a command line application anymore. What's the point of keeping the "vim" name apart from teasing users?
Call it neogvim or neogvimlikenotepadforjsfullstackdevelopper
Re: Neovim's Next Feature Poll
#15I've heard from a HN commentator that Neovim has given up on its principle goal of refactoring, and that progress has largely been due to uncrustify. Can anyone else speak to the health of the project?
I've been skimming the newsgroup(s) and browsing the commit logs for the past few weeks. It is definitely progressing.
I think they didn't quite realise how many people were going to want to be part of it, during the fund raising, and so a lot of effort has gone into coping with the large amount of work from multiple people, merging in patches from the 'main' VIM trunk, etc.
There's been a huge amount of pruning - which is still on-going - of old deprecated stuff. For instance, the X11 interface stuff is being simplified (for now) into just the GTK interface.
The original author of the neovim concept (Thiago) just posted: https://groups.google.com/forum/#!topic/neovim/R_jXItMXN4E saying that now he actually has someone to take over a lot of the community stuff, which should free him up to work hard on some of the original actual coding fundraising goals - which is excellent.
In some ways, thinking about it, it's probably good that he delayed it, as it means that there's been a lot of extra eyes going over the code of the whole project cleaning things up so that the new features aren't going to conflict too much with other bits being removed.
There's one of the guys who's a vimscript genius working on the lua/vimscript side of things, which will get merged in at some point once it's ready. It's essentially a completely separate project until it's ready though.
I suspect the first of the big project 'features' to be done will be the libuv stuff - which again, will have little to actually see as a user. Once that's done, and then the lua scripting stuff is done, after that then new features are possible.
Even now, though, the difference in the code is dramatic, and it's constantly getting minor cleanups and improvements along the way.
Re: Neovim's Next Feature Poll
#16How could they make a sublime-style code minimap in a CLI app?
The goal (as I understood it) is to separate back-end and front-end. That is, you could have a CLI front-end with just text interface, or a GUI front-end with all the fancy features.
Re: Neovim's Next Feature Poll
#17Loving the progress of Neovim so far, even better that notable plugin authors ( https://github.com/neovim/neovim/issues/622#issuecomment-415... ) are getting involved.
I've always wanted to write Vim plugins, but Vimscript and the RPC contortions always looked too hairy for me to get involved -- I'm excited for the new vim-embedding interface so I can get real VIM compatibility with my IDEs.
Except it has been possible for a long time to write scripts in other languages so what are you talking about?
Re: Neovim's Next Feature Poll
#18If that's not a command line application anymore. What's the point of keeping the "vim" name apart from teasing users? Call it neogvim or neogvimlikenotepadforjsfullstackdevelopper
You're free to continue using Vim, no one is taking that away from you. And if you would bother to read up on the project, you'd see that one of its primary goals is to separate the actual editor from the visual interface. That way, everything that is GUI related is separate.
Re: Neovim's Next Feature Poll
#19Do we know how Bram feels about Neovim and whether he is willing to get behind it if it succeeds?
The reason I ask is because one of the primary reasons I made the switch to Vim from TextMate is ubiquity and longevity. In the age of GitHub, fads, forks and abandoned projects have become all too common. Meanwhile Bram has proven himself to be a pillar-like benevolent dictator for decades, and to me that means a hell of a lot.
Re: Neovim's Next Feature Poll
#20Do we know how Bram feels about Neovim and whether he is willing to get behind it if it succeeds? The reason I ask is because one of the primary reasons I made the switch to Vim from TextMate is ubiquity and longevity. In the age of GitHub, fads, forks and abandoned projects have become all too common. Meanwhile Bram has proven himself to be a pillar-like benevolent dictator for decades, and to me that means a hell o…
Quoting his answer [1] in the vim_dev mailing list:
It's going to be an awful lot of work, with the result that not all
systems will be supported, new bugs introduced and what's the gain
for the end user exactly?
Total refactoring is not a solution. It's much better to improve what
we have. Perhaps with some small refactorings specifically aimed at
making Vim work better for users.