Hi Nikolay
I've turned your suggestion into a page about order of steps to fix Vim:
http://vim-wiki.mawercer.de/wiki/vim-development/fixing-vim-next-steps.html
Have a look at the (Comment ..) text, please add some samples. Code can
be added by
{{{
...
}}}
I've also added you as collaborator to
https://github.com/MarcWeber/vim-git-wiki.
See http://vim-wiki.mawercer.de/wiki/this-wiki/contributing.html
Duplicating my comments here so that items can be discussed.
(If you reply here I'll just update the comments)
Excerpts from Nikolay Pavlov's message of Mon Dec 02 08:41:43 +0100 2013:
> - Making vim embeddable (making it second point since it is even more
> refactoring).
Keep in mind that Yzis team failed on this, see
http://www.freehackers.org/VimIntegration (which was posted in this
thread earlier)
> - Stripping requirement to use VimL in Python/Ruby/Lua/etc interface. I.e.
> finishing what I started (I guess I can do this) for python and doing the
> similar thing for other languages.
I don't get you, can you elaborate?
> - Unicode support in regular expressions.
Can you also provide a simple use case, here ?
> - Possibly sane unicode indexing (may require further string refactoring to
> be efficient).
Use case ?
> - Non-string funcrefs (i.e. inclusion of my patch (without lambda part)).
> It contains fixes for some problems.
Again, just add a section to
http://vim-wiki.mawercer.de/wiki/topic/in-which-way-does-vim-suck.html
> - Stripping requirement to use shell to run applications.
Again, a use case would help much understanding what you mean exactly.
Marc Weber
--
--
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
---
You received this message because you are subscribed to the Google Groups
"vim_use" group.
To unsubscribe from this group and stop receiving emails from it, send an email
to vim_use+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/groups/opt_out.
