[slim-vim] Do others see this callback bug?

[Brad Beveridge]

On 17/08/06, Brad Beveridge <brad.beveridge at gmail.com> wrote:
> On 17/08/06, Brad Beveridge <brad.beveridge at gmail.com> wrote:
> > On 17/08/06, Mason Loring Bliss <mason at blisses.org> wrote:
> > > On Thu, Aug 17, 2006 at 08:19:30AM -0700, Brad Beveridge wrote:
> > >
> > > > For some reason, I noticed last night that this is now happening to me
> > > > ALL the time.  Does anybody else have this bug?  If so, is it recent?
> > >
> > > FWIW, I've seen something where I hit \x and then see nothing happen until
> > > I tap a key. I can't reliably reproduce this.
> > >
> > > Another oddity I seem to be able to reproduce: If I am at a point in a line
> > > where I get the automatic pop-up showing function arguments, if I type in a
> > > character, it doesn't show up on screen until I've typed another character.
> > >
> > > For instance, let's say I have this:
> > >
> > > (defun points (calories fat-grams dietary-fiber-grams)
> > >   (- (+ (/ calories 50)
> > >         (/ dietary-fiber-grams 12))
> > >      (/ (min dietary-fiber-grams 4)
> > >         5)))
> > > (points X
> > >
> > > ...where the 'X' marks the cursor position. I get the pop-up showing the
> > > desired arguments, but then any character I type is delayed until I type
> > > another character.
> > >
> > > This isn't precisely the same as what you're describing, but the symptoms
> > > are identical, so maybe it's a useful observation.
> > >
> > > I snagged tarballs afresh yesterday morning for this build.
> >
> > Thanks very much for the input Mason.  As you say, sometimes this bug
> > (from here on, I'll call it the select-hang bug) shows up, but is hard
> > to reproduce.  I seem to have managed to get into a state where it
> > happens all the time - maybe it is a good thing and we can get to the
> > bottom of it.
> >
> > As to the auto-argument-display, yes this is a known issue - its been
> > like that since I checked that code in.  So far it is in my "works
> > well enough" pile, but it can be a little disconcerting :)
> >
> > Cheers
> > Brad
> >
> I've got time for a quick email.  Basically, this is a bug I added due
> to not updating the screen from the network callback!  If you are a
> brave soul who is tracking all the checkins, hang tight - I'll have a
> fix in a couple of days.  Right now, I think that having this "not
> update the screen until next key" bug is a bit better than sometimes
> crashing in the callback.
> Or you can rollback the change in your tree.
>
> Cheers
> Brad
>
It appears that much of the flakeyness that I've been seeing on my
build in the past 2 days has been due to broken src/proto/*.pro files.
 They were giving be a build error, so I tried reverting to theclapp,
the error was still there.  I pulled from vanilla vim to replace the
*.pro files - ah, builds again.  However, strange brokeness -
apparently some of the pro files don't match the actual C files!!  So
I've rebuilt all my pro files, reverted the if_ecl.pro file, and all
is better (it would seem).
So, the moral of the story is - if you have build problems with the
*.pro files, regenerate them & talk to us, otherwise you will be a
very unhappy camper.

Cheers
Brad