On 2014-09-13 14:52, Bram Moolenaar wrote: > All this just for just for being able to use the "go" command... > Well, and some other functionality that uses byte offsets. > > Besides optimizing ml_updatechunk() for the use case of reading a > large file, another method would be to not keep anything updated > until "go" is actually used. I suspect most people don't use it at > all. It will have an impact on the first time "go" is used, but > not more than what is currently being done when reading a file.
I'm not "most people" apparently (though I suspected that to begin with) as I do use "go" occasionally. It's not frequent, and I personally wouldn't complain in this particular scenario if the first time I used it imposed a little byte-offset-calculation-delay. Most of the time I'm using Latin1 or 7-bit ASCCI files so it shouldn't be as big a deal. I've actually found "go" useless in multibyte files, as I'm usually not interested so much in the *byte* offset as in the *character* offset, and "go" can land you mid-character in such a file. -tim -- -- 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 [email protected]. For more options, visit https://groups.google.com/d/optout.
