[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
bug#43016: replace-region-contents takes a lot of time when called from
From: |
Eli Zaretskii |
Subject: |
bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer |
Date: |
Mon, 24 Aug 2020 20:27:30 +0300 |
> From: Tassilo Horn <tsdh@gnu.org>
> Cc: Eli Zaretskii <eliz@gnu.org>,
> "43016@debbugs.gnu.org" <43016@debbugs.gnu.org>,
> Paul Eggert <eggert@cs.ucla.edu>
> Date: Mon, 24 Aug 2020 19:14:50 +0200
>
> So basically I'd say the problem is in gnulib's compareseq. If it can't
> be fixed there, I see no other possibility than to stop using
> replace-buffer/region-contents in json.el (and wherever it might also be
> used). That would be sad because except for the performance in some
> cases, it's very nice. :-(
Could we decide whether to use replace-* functions dynamically, based
on the size of the region/buffer being prettified?
Btw, there's another problem with compareseq, see bug#42931. I guess
we need to add another criterion for early_abort, based on depth of
recursion?
Thanks.
- bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer, ljell, 2020/08/24
- bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer, Paul Eggert, 2020/08/24
- bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer, Eli Zaretskii, 2020/08/25
- bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer, Paul Eggert, 2020/08/25
- bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer, Tassilo Horn, 2020/08/25
- bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer, Paul Eggert, 2020/08/25
- bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer, ljell, 2020/08/24