On 7月17日, 上午2时19分, Marc Weber <marco-owe...@gmx.de> wrote:
> > 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 seenhttp://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
Thank you for your wish :-)
I just treat it as a practise. there are a amount of reasons to
improve Vim, not really full rewriting it.
for long line. I used to edit bookmark.htm generated by Firefox, it
contains BASE64 line for icons, and my Vim crashed... I had to use
notepad to do some work, that makes me thought about how to prefect
Vim.
Maybe rewritten is just some kinds of over excitation. but the really
thing I want is to change the philosophy of current Vim, just solve
out
the history remain issues, remove the parts that Vim had to hold, and
do
some courageous experiment about it. that's all.
--~--~---------~--~----~------------~-------~--~----~
You received this message from the "vim_dev" maillist.
For more information, visit http://www.vim.org/maillist.php
-~----------~----~----~----~------~----~------~--~---
