Am 2014-04-23 17:54, schrieb Ingo Karkat:
You seem to be really knowledgable about Vim's internals. The question
I
have in mind right now is whether you still feel comfortable about
those
"internal static variables", or whether you think this poses long-term
risks to Vim's stability.
For the current case, yes I believe it should be fixed correctly by
saving
and restoring all the static variables. But I am far from an expert on
the Vim
codebase and have probably already introduced too many bugs with my
patches.
I just enjoy hacking Vim code and trying to contribute.
Vim has gotten really complex in certain areas and sometimes it is hard
to figure
out what is going on (because of autocommands that might kick in
anywhere and result
in unexpected ways). So this is becoming more and more a problem.
At least some people think so, and have
suggested / started a complete rewrite (in a language like C++ that has
better means to avoid such).
You are talking about neovim? I keep an eye on it, but I am not sure, a
major
rewrite is such a good idea and they already seem to drop support for
certain
plattforms (even Windows, I think).
Is there anything (apart from more test coverage) that we can do with
the
current code base?!
Yes, tests would probably be very welcome. But I admit, writing them is
a huge
PITA. Even more then patching the actual core ;)
So anybody who likes to improve Vim by contributing tests is probably
very welcome
(can't talk for Bram, but I am sure he'll appreciate it).
Best,
Christian
--
--
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/d/optout.
