When Using vim solidity I get this error. I'm new to vim and lsp so I was wondering if I could get some advice on how to proceed to rectify this.

emit was introduced in v0.4.21 for events.

In your Readme section
Why you have put ?

No Plugin Manager

Copy all of the files manually into your ~/.vim.

What's the use of this.

A recent version of solidity added the constructor keyword.

contract OwnedToken {
    address owner;
    bytes32 name;

    constructor(bytes32 _name) public {
        owner = msg.sender;
        name = _name;
    }
}

Solidity doesn't support switch statements, so they shouldn't be a highlighted keyword.

http://solidity.readthedocs.io/en/develop/control-structures.html#control-structures

I am unsure what else to try. Here is my vimrc. Notably I have

filetype plugin indent on

and

set rtp+=~/.vim/bundle/vim-colorschemes/
set t_Co=256
" note: using Atom terminal color scheme for iTerm2
" (https://github.com/mbadolato/iTerm2-Color-Schemes/blob/master/schemes/Atom.itermcolors)
colorscheme herald
if has("syntax")
  syntax enable
endif

I have verified that the Vundle installation executed successfully

jamis@Jamiss-MBP:~/src/dotfiles$ tree ~/.vim/bundle/vim-solidity/
/Users/jamis/.vim/bundle/vim-solidity/
├── LICENSE
├── README.md
├── ftdetect
│   └── solidity.vim
├── ftplugin
│   └── solidity.vim
├── indent
│   └── solidity.vim
└── syntax
    └── solidity.vim

4 directories, 6 files](url)

Am I missing something major? Something conflicting in my vimrc? Maybe a conflicting Vundle plugin?

Before and After indent with gg=G

    event GameCreated(bytes32 indexed id, address indexed creator, string home,
        string away, uint16 indexed category, uint64 locktime);
    event BidPlaced(bytes32 indexed game_id, BookType book,
        address bidder, uint amount, bool home, int32 line);

    event GameCreated(bytes32 indexed id, address indexed creator, string home,
                      string away, uint16 indexed category, uint64 locktime);
                      event BidPlaced(bytes32 indexed game_id, BookType book,
                                      address bidder, uint amount, bool home, int32 line);

Any solution? Thank you!

If you chain several modifiers (or keywords) together, some do not get colored correctly:

function example()
         modifier1()
         constant
         modifier2()
         internal
         returns (bool)

For example:

pragma solidity ^0.4.23;

contract Test {
  string private constant MESSAGE = 'Syntax doesn\'t work';
}

This plugin sets expandtab, tabstop=4 and softtabstop=4 for solidity files, overriding the value they are set to in vimrc.

A syntax plugin should only override such settings if there are good reasons to do so, such as tabs and spaces indent having a different meaning (like in e.g. python). That is not the case in solidity and you are just trying to force your coding style on everyone.
Please don't.

Sorry to ask, but it would be useful to include some really basic installation guidance, even if it's just a link to other relevant documentation. I copied the directories to ~/.vim/ but that's as far as I've gotten.

Hello,

After installing the plug, I compared it with the ethereum package provided for Atom:

I ended up with this output in Vim:

The newbie I am in Programming would like to know why there are such differences in the syntax highlighting.
Is there room for improving the actual Vim syntax highlighting ? It lacks items such as def | extern | self. | msg.sender | deposit | data, etc.... It does not recognize functions after 'def' for instance.
Otherwise, is there a way for me to change this by my own ?
Thanks.

There is a library keyword now which appears in the same places as contract

like in javascript

The syntax highlighting only works, if vim is configured to use 256 colors. I think this should be reflected in the README.

• type and is from user defined value type definitions.
• from and as from import directives

You can find a maintained fork at https://github.com/thesis/vim-solidity

Seems like multiline comments might confuse vim-solidity. Having said that, I am using editorconfig, so if you can't reproduce, that might be where we diverge :)

contract SimpleStorage {
    uint storedData;

    /** 
    *
   *
  *
 *
    */
    function set(uint x) {
        storedData = x;
    }