Eric Arnold wrote:
I haven't been idle on this. I was unable to get my test case working
for a simple but un-obvious reason. It requires that at least one
other window be open.
Run the following, and open two windows. Edit a file in one. Open a
new line, which I assume triggers the
On Tue, May 02, 2006 at 02:17:58PM +0200, Bram Moolenaar wrote:
Eric Arnold wrote:
I haven't been idle on this. I was unable to get my test case working
for a simple but un-obvious reason. It requires that at least one
other window be open.
Run the following, and open two
On 5/2/06, Bram Moolenaar [EMAIL PROTECTED] wrote:
Benji Fisher wrote:
On Tue, May 02, 2006 at 02:17:58PM +0200, Bram Moolenaar wrote:
Eric Arnold wrote:
I haven't been idle on this. I was unable to get my test case working
for a simple but un-obvious reason. It requires that at
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
On 5/1/06, Eric Arnold [EMAIL PROTECTED] 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
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
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
