21

Proposal: Vi and vim

Seems like NeoVim (the engine) would make sense to be included, but what about NeoVim front ends?

14

I don't see any reason why it wouldn't be. It's part of the vim ecosystem. In spite of major philosophical differences driving the project it is still largely compatible with vim and the expertise involved will largely cross over.

SE sites are scoped around areas of expertise rather than specific products, much less versions of those products. All aspects of the vim ecosystem including but not limited to program usage, configuration, plugin and scripting issues, as well as development should be on topic provided the questions themselves fit the SE model of answerable questions (i.e. not just open discussion topics).

Neovim fits this area of expertise as much as vim does.

  • 3
    I agree with you, though I think we should probably make it clear that bug reports a far more useful when sent to the project, not us. – derobert Jan 23 '15 at 17:34
  • @derobert Yes. Program centric or not, SE sites are QnA sites not bug trackers. – Caleb Jan 23 '15 at 17:35
8

This question was raised on the old (deleted) vim/vi proposal. The consensus there was that neovim should be on-topic as soon as there was a release.

This was to ensure that neovim questions on vim.SX wouldn't be what would eventually become obsolete bug reports on a pre-alpha.

From the neovim website

Neovim is currently under development, and no releases have been published yet. To install a pre-alpha [...]

Unfortunately, it's not clear when this will be the case

When will a beta be available?
When it's ready.

  • This isn't a technical support website or a bug-tracker. I'm not sure why the release version number of something in the vim ecosystem for which the expertise is nearly a 100% match for this site should be relevant at all. – Caleb Jan 23 '15 at 17:18

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .