Excerpts from Tony's message of Thu Jan 16 07:07:35 +0100 2014: > Can someone open a gist / wiki / create an INTERNALS.txt or doc file > for developers to have a broad overview of how vim works internally?
I've started this wiki to document patches / efforts / idea to improve the situation. I started by documenting why "vim sucks": http://vim-wiki.mawercer.de/wiki/index.html One of the main issues is: - documenting source does not add value - patching Vim would, but which is the best upstream for Vim? Do we want to keep using C (I don't think so, because even Bram sayd that coding higher level stuff in C is tough) I personally would like to find ways to share code with other editors, too. I very sure that C is the wrong tool to do so. Maybe it does not exist. I and Zyx (and Shougo) have started a community repository on bitbucket, and we welcome everybody to join. There is a small amount of projects which could benefit from allowing people to join and improve easily. I even think about 'what would happen splitting runtime from Vim, and upload it to bitbucket / github' ? That's my (biased) view on this topic. The wiki can be edited easily, so consider adding your ideas. I chose to write a new wiki because I wanted people being able to edit simple text files with Vim to keep it up to date easily. Another problem is that Vim is "broken" in some ways - see the "resize" thing mentioned on my wiki. So I'm unsure wether documenting it really helps - fixing would eventually require introducing threading etc - and that would be quite some work - and I'd eventually would prefer doing this in a higher level language. Marc Weber -- -- You received this message from the "vim_dev" 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 --- You received this message because you are subscribed to the Google Groups "vim_dev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. For more options, visit https://groups.google.com/groups/opt_out.
