Re: table.el 1.6.1

[Kim F. Storm]

"Stefan Monnier" <monnier+gnu/address@hidden> writes:

> > Richard Stallman <address@hidden> writes:
> > 
> > >     I think it would be simpler to do an update whenever point moves in or
> > >     out of an interval -- it may be a little wasteful, but we already have
> > >     all the necessary information to do that in set_point_both, 
> > > 
> > > It is very wasteful and not much simpler.  This would update the menu
> > > bar due to changes in point within a function.  The right way would
> > > only look at point when it is time to read a command.
> > 
> > Considering that simply turning on column-number-mode causes
> > a mode-line/menu-bar/tool-bar update after every command, this
> > is at least an order of magnitude less wasteful than doing that.
> 
> That's not true.  Doing it once per command might be OK.
> But doing it once per point-motion is a lot more work because
> a single command might do many point motions.
> 
> I.e. it should not be done from set_point_both but from the main
> command loop (after each command, check if the text properties under
> point have changed).

I don't follow...

AFAIK, incrementing update_mode_lines causes the mode line to
be updated on the next redisplay -- i.e. only once per command,
no matter how many times you set it...

-- 
Kim F. Storm <address@hidden> http://www.cua.dk