vim/vim-snippets
1
0
Fork 0
Code Issues Pull Requests Releases Wiki Activity

merging "contributing notes" into "Policies for contributors" - thanks lucc

Browse Source
This commit is contained in:
Marc Weber 2014-05-06 13:13:44 +02:00
parent 2f5e1dace4
commit 9376b6ea35
1 changed files with 7 additions and 14 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

21
README.md
View File

@ -130,6 +130,13 @@ What about one line if ee then .. else .. vs if \n .. then \n ... \n else \n ..
Which additional policies to add?
Discuss at: https://github.com/honza/vim-snippets/issues/230
*folding markers*:
Until further work is done on `vim-snipmate`, please don't add folding markers
into snippets. `vim-snipmate` has some comments about how to patch all snippets
on the fly adding those.
Currently all snippets from UltiSnips have been put into UltiSnips - some work
on merging should be done (dropping duplicates etc). Also see engines section above.
Related repositories
--------------------
@ -206,20 +213,6 @@ This list is kept up-to-date on a best effort basis.
* Falcon - [steveno](https://github.com/steveno)
* Elixir - [iurifq](https://github.com/iurifq)
Contributing notes
------------------
Until further work is done on `vim-snipmate`, please don't add folding markers
into snippets. `vim-snipmate` has some comments about how to patch all snippets
on the fly adding those.
Because UltiSnips reads snipmate-snippets too there is no need to duplicate all
snippets - only those snippets who use advanced UltiSnips features should be
duplicated in UltiSnips.
Currently all snippets from UltiSnips have been put into UltiSnips - some work
on merging should be done (dropping duplicates etc)
License
-------