[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: |
Tue, 17 Mar 2015 09:08:15 +0200 |
> Date: Mon, 16 Mar 2015 13:43:57 -0700
> From: Daniel Colascione <address@hidden>
> CC: address@hidden, address@hidden
>
> > My understanding was that Stefan wants these hooks replaced with
> > different ones, not throw them away. So I was talking about those
> > different hooks.
>
> I don't see a good use case for either the old or the new hook. Instead
> of making point motion updates "edge triggered" (i.e., run a function
> when point enters or exits a certain region), modes should be using a
> "level triggered" approach, where they inspect the current location of
> point and update whatever state they need based on that current location.
There are a lot of features in Emacs that might make little sense to
me or you or someone else. Removing features just because of that, or
because we think they don't have use cases that are valid in our eyes,
is not a practice I'd recommend. At least, we never did that in
Emacs, AFAIR. Features might be deprecated because they cause real
damage to Emacs development, but even then we do that very cautiously
and slowly.
My $0.02, anyway.
- Re: Can we make set_point_both less expensive?, (continued)
- 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
- Re: Can we make set_point_both less expensive?,
Eli Zaretskii <=
- RE: Can we make set_point_both less expensive?, Drew Adams, 2015/03/17
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/16
- Re: Can we make set_point_both less expensive?, martin rudalics, 2015/03/17
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/17
- Re: Can we make set_point_both less expensive?, martin rudalics, 2015/03/17
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/17
- Re: Can we make set_point_both less expensive?, martin rudalics, 2015/03/18
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/18
- Re: Can we make set_point_both less expensive?, martin rudalics, 2015/03/18
- Re: Can we make set_point_both less expensive?, Stefan Monnier, 2015/03/18