GNU bug report logs - #62780
30.0.50; Redisplay gets slow when using Org tables + show-trailing-whitespace

Previous Next

Full log

Message #68 received at 62780 <at> debbugs.gnu.org (full text, mbox):

From: Eli Zaretskii <eliz <at> gnu.org>
To: Ihor Radchenko <yantar92 <at> posteo.net>
Cc: 62780 <at> debbugs.gnu.org
Subject: Re: bug#62780: 30.0.50; Redisplay gets slow when using Org tables +
 show-trailing-whitespace
Date: Fri, 14 Apr 2023 18:06:29 +0300

> From: Ihor Radchenko <yantar92 <at> posteo.net>
> Cc: 62780 <at> debbugs.gnu.org
> Date: Fri, 14 Apr 2023 14:56:13 +0000
> 
> Eli Zaretskii <eliz <at> gnu.org> writes:
> 
> >> I see. But can the same limit be re-used for static compositions?
> >
> > Which limit is that?
> 
> I am referring to limit in compute_stop_pos. It is unused
> when calling composition_compute_stop_pos.

You want to reduce the limit inside composition_compute_stop_pos from
500 to 100?  If you try that, does it speed up this scenario enough to
consider such a change?

> Of course, if your idea with completely bypassing
> composition_compute_stop_pos call works, it will be even better.

We cannot bypass composition_compute_stop_pos in compute_stop_pos,
because it also looks for auto-composable characters, those controlled
by composition-function-table.  But I think we _can_ avoid calling
find_composition from composition_compute_stop_pos in this particular
case.

Previous Next

GNU bug tracking system
Copyright (C) 1999 Darren O. Benham, 1997,2003 nCipher Corporation Ltd, 1994-97 Ian Jackson.