3 ms·
I wonder if it's stable on Windows now. I tried 0.2.0 but it felt more like a proof of concept. To be honest the version number kind of implies that this is not
by oblio 9y ago
I wonder if it's stable on Windows now. I tried 0.2.0 but it felt more like a proof of concept. To be honest the version number kind of implies that this is not a super-stable version :)
- fmoralesc 9y agoA lot of work seems to have gone into the windows version for 0.2.1, I would try it again.
- superflyguy 9y agoIt's not, I still get a white background I cannot change, even with nvim-qt -- -u NORC. It's been fine on Linux for ages.
- seren 9y agoFrom a quick test, :terminal did not work on my windows setup on 0.2, it is now working (which is a least a new feature of neovim vs vim)
- justinmk 9y agoEvery Neovim release is considered stable. The leading zero means we may break backwards-compatibility in some cases (but we rarely do; we are considering 1.0 after 0.3 is finished).
- oblio 9y agoFor Windows, are you adopting a GUI as part of the packages supported by the official devs? A GUI-less Windows editor isn't of much use, especially considering the rather sorry state of Windows terminals (even with the enhancements in Windows 10).
- justinmk 9y agoThe Windows packages include a GUI. https://github.com/neovim/neovim/releases https://github.com/neovim/neovim/releases
- oblio 9y agoYes, I know, I has just checking if it's there to stay for 1.0. Good to know that it is! :) (Off-topic: you guys rock, I hope the Neovim vision of a high quality Vim component scriptable picks up steam and maybe one day in the distant future Neovim powers a top-notch IDE powered by Lua scripts, instead of the ugh Vimscript ones)
- epage 9y agoIs the windows GUI advertised in any way, like screenshots, feature lists, etc? If it wasn't for your post, I wouldn't have known this even existed. Now that I do know, I'm wanting to know more before I bother trying.
- erikb 9y agoI think you interpret that correctly.