[Top][All Lists]
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: table.el 1.6.1
From: |
Miles Bader |
Subject: |
Re: table.el 1.6.1 |
Date: |
01 Apr 2002 06:56:44 +0900 |
address@hidden (Kim F. Storm) writes:
> The point-entered and point-left properties are handled in
> set_point_both, so if point leaves and reenters the same interval
> due to executing a command, those hooks are executed (superfluously?)
The point-entered and point-left properties _must_ be handled in this
manner, because they're open ended -- users can add any sort of hook
they want, and such hooks might actually depend on this behavior.
> Since my idea of doing a mode-line update in the same place if
> an interval is left or entered -- and you argue that is not the
> proper place
The mode-line state (by contrast) only depends on the position of point
at the instant of redisplay, so recalculating every time point moves
will often be wasted effort.
-Miles
--
"Most attacks seem to take place at night, during a rainstorm, uphill,
where four map sheets join." -- Anon. British Officer in WW I
- Re: table.el 1.6.1, (continued)
- Re: table.el 1.6.1, Tak Ota, 2002/03/22
- Re: table.el 1.6.1, Richard Stallman, 2002/03/23
- Re: table.el 1.6.1, Kim F. Storm, 2002/03/23
- Re: table.el 1.6.1, Richard Stallman, 2002/03/24
- Re: table.el 1.6.1, Stefan Monnier, 2002/03/25
- Re: table.el 1.6.1, Kim F. Storm, 2002/03/25
- Re: table.el 1.6.1, Richard Stallman, 2002/03/28
- Re: table.el 1.6.1, Kim F. Storm, 2002/03/28
- Re: table.el 1.6.1, Richard Stallman, 2002/03/29
- Re: table.el 1.6.1, Kim F. Storm, 2002/03/31
- Re: table.el 1.6.1,
Miles Bader <=
table.el 1.6.3, Tak Ota, 2002/03/22