You don't need to repeat yourself. If I could give you a reproducible code fragment, I would. It happens as part of a relatively long script.
It's a *data point*. A piece of information. "Setting highlighting from the tabline function causes it to re-trigger on the next keystroke". In this case, it's a rather specific piece of information. Once again, I'm not demanding a fix. I'm not asking you to guess what I'm doing, but why not let you know about this? I'm only asking you to think about it a little. You might get a sudden idea, since you're the one who knows the Vim code. You could at least file it away. If you gather pieces of information about a project, you eventually get correlations which are useful! However, if you can't use partial information for *anything*, then I'm nonplussed, would be the word. If you want silence from users are unable to give a definitive test case, while trying to *guess* what the Vim code is doing, that seems counter-productive. On 5/1/06, Bram Moolenaar <[EMAIL PROTECTED]> wrote:
Eric Arnold wrote: > I think I've found the thing that triggers my problem with > TabLineSet.vim where the tabline function get called for every > keystroke: I reset the highlighting in the tabline function. > > Does it seem reasonable that the highlighting changes are triggering > the tabline to re-update (and thus creating a loop)? How many times do I need to repeat this: Pleeeeease give a reproducable example. I don't have time to guess what you are doing. -- If you don't get everything you want, think of everything you didn't get and don't want. /// Bram Moolenaar -- [EMAIL PROTECTED] -- http://www.Moolenaar.net \\\ /// sponsor Vim, vote for features -- http://www.Vim.org/sponsor/ \\\ \\\ download, build and distribute -- http://www.A-A-P.org /// \\\ help me help AIDS victims -- http://ICCF-Holland.org ///
