From: Lars Ingebrigtsen <larsi@gnus.org>
To: Tassilo Horn <tsdh@gnu.org>
Cc: ljell <laszlomail@protonmail.com>,
"43016@debbugs.gnu.org" <43016@debbugs.gnu.org>,
Paul Eggert <eggert@cs.ucla.edu>
Subject: bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer
Date: Mon, 24 Aug 2020 19:21:24 +0200 [thread overview]
Message-ID: <87pn7g6ju3.fsf@gnus.org> (raw)
In-Reply-To: <875z98c6et.fsf@gnu.org> (Tassilo Horn's message of "Mon, 24 Aug 2020 19:14:50 +0200")
Tassilo Horn <tsdh@gnu.org> writes:
> That would be sad because except for the performance in some
> cases, it's very nice. :-(
It is indeed very nice. My guess is that most of the usages of the
function is for shortish JSON structures. Perhaps we could just
introduce an arbitrary switchover between using replace-region-contents
and plain replacing -- like a hundred K or something?
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2020-08-24 17:21 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-08-24 8:25 bug#43016: replace-region-contents takes a lot of time when called from json-pretty-print-buffer ljell via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-24 10:37 ` Eli Zaretskii
2020-08-24 12:13 ` ljell via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-24 12:29 ` ljell via Bug reports for GNU Emacs, the Swiss army knife of text editors
2020-08-24 17:14 ` Tassilo Horn
2020-08-24 17:21 ` Lars Ingebrigtsen [this message]
2020-08-24 17:25 ` Philipp Stephani
2020-08-24 17:27 ` Eli Zaretskii
2020-08-24 19:15 ` Tassilo Horn
2020-08-24 19:36 ` Eli Zaretskii
2020-08-24 23:35 ` Paul Eggert
2020-08-25 6:10 ` Eli Zaretskii
2020-08-25 18:26 ` Paul Eggert
2020-08-25 17:30 ` Tassilo Horn
2020-08-25 18:19 ` Paul Eggert
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=87pn7g6ju3.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=43016@debbugs.gnu.org \
--cc=eggert@cs.ucla.edu \
--cc=laszlomail@protonmail.com \
--cc=tsdh@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
Code repositories for project(s) associated with this external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.