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."

• Syntax highlighting problems would be a nice fix Syntax highlighting problems would be a nice fix (Score: 5, Insightful) by fliptop on Thursday March 20 2014, @12:52PM

  by fliptop (1666) on Thursday March 20 2014, @12:52PM (#18950) Journal

  It lets you extend the editor in any programming language

  Just last night I forked/cloned the SN git repo and took a look at Environment.pm in vim. The following line in the prepareUser method has a regex that screws up the syntax highlighting for the rest of the code:

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

  I changed it to:

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

  which fixed it, but the original code is syntatically correct. Like I said, just getting stuff like that fixed would be a good thing, IMHO.

  --
  If you have second thoughts about booking a trip to an Indian casino, is it a reservation reservation reservation?

  Starting Score:	1		point
  Moderation		+3
  Insightful=2, Interesting=1, Total=3
  Extra 'Insightful' Modifier		0
  Karma-Bonus Modifier		+1
  Total Score:		5

• Re:Syntax highlighting problems would be a nice fi Re:Syntax highlighting problems would be a nice fi (Score: 1) by The Mighty Buzzard on Thursday March 20 2014, @01:07PM

  by The Mighty Buzzard (18) <themightybuzzard@soylentnews.org> on Thursday March 20 2014, @01:07PM (#18956) Journal

  Erm, that's the exact same meaning in perl. Unless there's a bug in the perl version, there should be absolutely no difference between m[^/$], m{^/$}, or even m#^/$#.

  --
  123
  456
  789

  Parent

  • Re:Syntax highlighting problems would be a nice fi Re:Syntax highlighting problems would be a nice fi (Score: 2) by The Mighty Buzzard on Thursday March 20 2014, @01:12PM

    by The Mighty Buzzard (18) <themightybuzzard@soylentnews.org> on Thursday March 20 2014, @01:12PM (#18960) Journal

    Yeah, feel free to ignore the above post. Believe I'll go with Way Too Much Coffee as my excuse for failing at basic reading comprehension.

    --
    123
    456
    789

    Parent

    • Re:Syntax highlighting problems would be a nice fi (Score: 2) by fliptop on Thursday March 20 2014, @02:09PM

      by fliptop (1666) on Thursday March 20 2014, @02:09PM (#18990) Journal

      I'll go with Way Too Much Coffee as my excuse

      No worries, after rereading my comment I probably could've worded it more clearly anyway.

      --
      If you have second thoughts about booking a trip to an Indian casino, is it a reservation reservation reservation?

      Parent

• Re:Syntax highlighting problems would be a nice fi (Score: 2) by TheRaven on Friday March 21 2014, @05:08AM

  by TheRaven (270) on Friday March 21 2014, @05:08AM (#19201) Journal

  My issue with vim's highlighting is that it does not differentiate between spacing for indent and spacing for alignment. Our coding style says that you must indent one tab for every indent level, but may use spaces to align code. For example, if you have an if statement that wraps, the next line would have the same number of tabs as the preceding one, but then 4 spaces to line up with the character after the ( of the if statement. Other continued lines follow the same rule. If you're lining up comments or variable declarations, you similarly use spaces.

  --
  sudo mod me up

  Parent

• 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