On Feb 20, 9:07 pm, Marc Weber <marco-owe...@gmx.de> wrote: > I feel thatwww.vim.orgcontents are outdated - and I'd likewww.vim.org > answering common questions such as: > - how to use Vim for python development > - how to configure Vim for coding C/C++ > - how to does a common .vimrc look like ? > maybe even add a .vimrc configurator and everybody can provide > snippets? > Example how it could look like:http://mootools.net/core/ > However there are much more item - thus a JS based filter by > keywords would be nice. > - ... > > On #vim pages likehttp://sontek.net/turning-vim-into-a-modern-python-ide#id21 > are references (which is a good thing) - BUT: > > - it still references old msanders snipmate repo > > - it does not talk about pyton repl with completion implementations > which are available for Vim (such as vim-addon-async) > > That's why I think that we should add kind of "wiki" towww.vim.org. > Modifying it should be dead simple (like adding snippets to > snipmate-snippets). That's why I consider providing any git based > wiki system people can either edit online or by cloning the git repo > into any dir and modifying the source files directly. > This also means that you can browse / read everything offline. > > The format used in text files should be dead simple such as vim help > file syntax or markdown like syntax. (I also know that there are many > wiki like plugins for Vim). > > Even if its not 'official' at the beginning - such a page could be > created and added integrated intowww.vim.orglater at some stage. > > How do you feel about such a change? Would you appreciate it? >
Why not a real wiki with real wiki syntax? Or why not just create pages on the existing wikia.com wiki with prominent links from vim.org? code.google.com also provides a wiki, IIRC. I don't see a need to create something new. -- You received this message from the "vim_use" maillist. Do not top-post! Type your reply below the text you are replying to. For more information, visit http://www.vim.org/maillist.php
