> system (since history issue, Vim's undo system is more or less > terrible), and a flesh new parser-base highlight system. all in all, Have you seen http://www.vim.org/soc/ideas.php ?
About your long line use case: I don't think you have to edit this kind of files very often. In fact I never did. So I consider this being a corner case I'm not interested in. I could use bvi for such files. If you're that good at C I'd write a short C app which splits the long lines LLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGONG LONG into LLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG == AUTO SPLIT === LONGLONG LONGLONG LONGLONG LONGLONG LONGLONG LONGONG LONG so that you can join them again later. Yeah it's a workaround. but you can open the file in vim then and it will take less time than rewriting parts of vim. I don't want you stopping your work on improving vim. But I don't think this use case in particular is that important. I wish you good luck, some help provided by this list and ... much spare time.. Yours Marc Weber --~--~---------~--~----~------------~-------~--~----~ You received this message from the "vim_dev" maillist. For more information, visit http://www.vim.org/maillist.php -~----------~----~----~----~------~----~------~--~---
