[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#56682: locked narrowing
From: |
Eli Zaretskii |
Subject: |
bug#56682: locked narrowing |
Date: |
Fri, 02 Dec 2022 14:02:53 +0200 |
> Date: Fri, 02 Dec 2022 09:16:08 +0000
> From: Gregory Heytings <gregory@heytings.org>
> cc: monnier@iro.umontreal.ca, 56682@debbugs.gnu.org, dgutov@yandex.ru
>
> In which case we are back to the alternative solution, which is to trigger
> rescanning on each redisplay cycle. Which might, after all, be the
> simplest and safest solution.
If the region we scan is limited by some reasonably large size, that could
indeed be the best solution.
- bug#56682: locked narrowing, (continued)
- bug#56682: locked narrowing, Gregory Heytings, 2022/12/02
- bug#56682: locked narrowing, Stefan Monnier, 2022/12/02
- bug#56682: locked narrowing, Eli Zaretskii, 2022/12/02
- bug#56682: locked narrowing, Gregory Heytings, 2022/12/02
- bug#56682: locked narrowing, Eli Zaretskii, 2022/12/02
- bug#56682: locked narrowing, Gregory Heytings, 2022/12/02
- bug#56682: locked narrowing,
Eli Zaretskii <=
- bug#56682: locked narrowing, Eli Zaretskii, 2022/12/02
- bug#56682: locked narrowing, Gregory Heytings, 2022/12/02
- bug#56682: locked narrowing, Eli Zaretskii, 2022/12/02
- bug#56682: locked narrowing, Gregory Heytings, 2022/12/02
- bug#56682: locked narrowing, dick, 2022/12/02
bug#56682: locked narrowing, Juri Linkov, 2022/12/06