Slash Boxes

SoylentNews is people

posted by janrinok on Thursday March 20 2014, @04:27PM   Printer-friendly
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."

This discussion has been archived. No new comments can be posted.
Display Options Threshold/Breakthrough Mark All as Read Mark All as Unread
The Fine Print: The following comments are owned by whoever posted them. We are not responsible for them in any way.
  • (Score: 2) by TheRaven on Friday March 21 2014, @09:08AM

    by TheRaven (270) on Friday March 21 2014, @09: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
    Starting Score:    1  point
    Karma-Bonus Modifier   +1  

    Total Score:   2