{"action":"opened","issue":{"url":"https://api.github.com/repos/Shougo/neobundle.vim/issues/450","labels_url":"https://api.github.com/repos/Shougo/neobundle.vim/issues/450/labels{/name}","comments_url":"https://api.github.com/repos/Shougo/neobundle.vim/issues/450/comments","events_url":"https://api.github.com/repos/Shougo/neobundle.vim/issues/450/events","html_url":"https://github.com/Shougo/neobundle.vim/issues/450","id":117007606,"number":450,"title":"Why TOML instead of YAML?","user":{"login":"amerlyq","id":5730096,"avatar_url":"https://avatars.githubusercontent.com/u/5730096?v=3","gravatar_id":"","url":"https://api.github.com/users/amerlyq","html_url":"https://github.com/amerlyq","followers_url":"https://api.github.com/users/amerlyq/followers","following_url":"https://api.github.com/users/amerlyq/following{/other_user}","gists_url":"https://api.github.com/users/amerlyq/gists{/gist_id}","starred_url":"https://api.github.com/users/amerlyq/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/amerlyq/subscriptions","organizations_url":"https://api.github.com/users/amerlyq/orgs","repos_url":"https://api.github.com/users/amerlyq/repos","events_url":"https://api.github.com/users/amerlyq/events{/privacy}","received_events_url":"https://api.github.com/users/amerlyq/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-11-15T17:53:54Z","updated_at":"2015-11-15T17:53:54Z","closed_at":null,"body":"And so it is -- exactly same question as in the header. \r\nWhy not Yaml? It's much more neat and clean considering nested lists.\r\nYou can drop ```[[plugins]]``` marker, using exact repo name as root key,  skip quotes on strings, make nesting more stand out, reuse identical config sections by back-references...\r\n\r\nNow I, of course, can use something like 3rd-party [pre-generation of plugins.vim](http://genkisugimoto.com/blog/manage-vim-plugins-via-yaml/) but native solution would be much better."}}