[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 18:23:05 +0200 |
> From: Stefan Monnier <address@hidden>
> Cc: address@hidden, address@hidden
> Date: Mon, 16 Mar 2015 08:47:47 -0400
>
> what users of those features normally want is to catch movement of
> the cursor
You mean, we should do this in redisplay? Wouldn't that be a radical
change in semantics? In particular, if redisplay doesn't run, neither
will the hooks.
- Can we make set_point_both less expensive?, Daniel Colascione, 2015/03/15
- 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 <=
- 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?, 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