[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: Can we make set_point_both less expensive?
From: |
Eli Zaretskii |
Subject: |
Re: Can we make set_point_both less expensive? |
Date: |
Mon, 16 Mar 2015 20:05:35 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Mon, 16 Mar 2015 13:36:40 -0400
>
> >> what users of those features normally want is to catch movement of
> >> the cursor
> > You mean, we should do this in redisplay?
>
> Probably in pre-redisplay-hook or in pre/post-command-hook, yes.
That contradicts the "catch movement of cursor" idea: redisplay could
well move point from where it is found before redisplay, as you know.
- Re: Can we make set_point_both less expensive?, (continued)
- Re: Can we make set_point_both less expensive?, Eli Zaretskii, 2015/03/15
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/16
- Re: Can we make set_point_both less expensive?, Eli Zaretskii, 2015/03/16
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/16
- Re: Can we make set_point_both less expensive?,
Eli Zaretskii <=
- Re: Can we make set_point_both less expensive?, Daniel Colascione, 2015/03/16
- Re: Can we make set_point_both less expensive?, Eli Zaretskii, 2015/03/16
- Re: Can we make set_point_both less expensive?, Daniel Colascione, 2015/03/16
- Re: Can we make set_point_both less expensive?, Eli Zaretskii, 2015/03/16
- Re: Can we make set_point_both less expensive?, Daniel Colascione, 2015/03/16
- Re: Can we make set_point_both less expensive?, Lennart Borgman, 2015/03/16
- Re: Can we make set_point_both less expensive?, Daniel Colascione, 2015/03/16
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/16
- Re: Can we make set_point_both less expensive?, Eli Zaretskii, 2015/03/17
- RE: Can we make set_point_both less expensive?, Drew Adams, 2015/03/17