Dev.SN

NeoVim: Vim's Re-birth for the 21st Century

posted by janrinok on Thursday March 20 2014, @12:27PM   
from the cue-vim-emacs-war-in-5-4-3-2-1 dept.

Hell_Rok writes:

"Neovim is an effort to aggressively re-factor the Vim source code and improve on:

• It will provide first class support for embedding.
• It lets you extend the editor in any programming language.
• It supports more powerful GUIs.
• Vim plugins will work with it.

Hosted on Bounty Source it has reached $25,500 of it's goal of $10,000, although there are still 3 days to reach further stretch goals! You can view the projects current progress and even pitch in over at GitHub. As someone who has started using Vim full-time over the last 6 months I feel that this is a very good project for the longevity of Vim."

• Re:Syntax highlighting problems would be a nice fi (Score: 1) by michealpwalls on Friday March 21 2014, @10:27AM

  by michealpwalls (3920) on Friday March 21 2014, @10:27AM (#19314) Homepage

  "just getting stuff like that fixed would be a good thing, IMHO.

  That is the point, I think. The vim code-base is ancient and very large, filled with old and largely unfamiliar dialects of C (C'89) that few would be able to find and correct bugs, regardless of how trivial they may appear.

  I think, the whole point is to refactor out that code to make fixing trivial bugs like that much, much more easier. The largest problem with open source projects isn't fixing bugs, it's actually getting into the codebase and finding what it is you're looking for... When you're a volunteer, wading through 300k lines of foreign C89 code you've never seen in your life isn't exactly what I call a good day. Not only that, but being unfamiliar with the dialect will quickly destroy your courage to make any changes, for fear of outright breaking it :)

  As an aside, my PERL is pretty rusty but I think both are syntactically correct:

  if ($uri =~ m[^/$]) {
  
  =
  
  if ($uri =~ m{^/$}) {

  Parent