Comment #4 on issue 274 by [email protected]: hangs with very long lines
https://code.google.com/p/vim/issues/detail?id=274
I guess it must be syntax highlight, though I haven't tried disabling it
yet.
I was actually just reading the file without modifying it (I hadn't opened
it in readonly, but I didn't do any modifications, I only moved the cursor
up and down).
You shouldn't need a plugin in order to manage large files efficiently.
I'm not sure whether the problem here is large file or very long lines. If
managing a very long line is more problematic than managing the same text
split in smaller lines (whether it's because of syntax highlight or not),
then there is something wrong.
If syntax highlight is the problem and it's unavoidable (i.e. there's no
known algorithm to manage it without the cost growing with the size of the
file), then a warning should be shown when it starts being a problem,
allowing the user to switch it off. It is never acceptable that the
interface (even if it is a text-based interface) stops responding.
Also, after several minutes without touching it, vim was still processing
every single keystroke from minutes earlier. That is, if I had hit the up
and down arrow keys several times, you would see the text scrolling up one
line, then after several seconds or more than a minute, up one more line,
and so on.
I'm not sure if all keystrokes are queued up and processed blindly
regardless of wheter or not there are more keystrokes in the queue, but if
that is the case (as it seems to be), then that's wrong too. If the program
gets blocked processing a command, and after that, there are several
consecutive keystrokes in the queue that are merely cursor movements, it
should not process each one and display the result of each one, it should
just sum up the movements and process one single move; e.g. if you have hit
the up key 5 times and the down key 9 times, instead of processing every
single keystroke and "render" the result for each one, it should just move
down 4 lines and render the final result. Even if more complex sequences of
commands are "queued" while rendering can't keep the pace, and they need to
be processed one by one, the "rendering" should still be skipped unless
it's necessary in order to process the next command (e.g. the position of
the cursor needs to be known). Syntax highlight can *certainly* always be
skipped.
--
You received this message because this project is configured to send all
issue notifications to this address.
You may adjust your notification preferences at:
https://code.google.com/hosting/settings
--
--
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.
