From: Eli Zaretskii <eliz@gnu.org>
To: Michael Eliachevitch <m.eliachevitch@posteo.de>
Cc: yantar92@posteo.net, 58687@debbugs.gnu.org
Subject: bug#58687: 29.0.50; Enabling pp-use-max-width dramatically slows down formatting of large sexps like org-persist--index
Date: Fri, 13 Jan 2023 10:42:48 +0200 [thread overview]
Message-ID: <83o7r2akqf.fsf@gnu.org> (raw)
In-Reply-To: <87cz7j8j5o.fsf@posteo.de> (message from Michael Eliachevitch on Thu, 12 Jan 2023 22:22:20 +0000)
> From: Michael Eliachevitch <m.eliachevitch@posteo.de>
> Cc: Ihor Radchenko <yantar92@posteo.net>, 58687@debbugs.gnu.org
> Date: Thu, 12 Jan 2023 22:22:20 +0000
>
> On 2023-01-12 at 18:39 +02, Eli Zaretskii <eliz@gnu.org> wrote:
>
> > Not "the current 'pp'", but the implementation for this optional
> > behavior.
>
> This is optional behavior, but I would prefer if the performance impact of enabling this optional behavior would be documented, e.g. in the variable docstring and NEWS.29.
Done.
> On 2023-01-12 at 22:03 +0530, Visuwesh <visuweshm@gmail.com> wrote:
>
> > Personally, I always thought it would be best if the user facing
> > commands like pp-eval-sexp and friends alone respected the user option.
>
> Sounds like a good idea.
Also done. (Most of the functions already honored this option, but 2
of them didn't.)
next prev parent reply other threads:[~2023-01-13 8:42 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-10-21 12:59 bug#58687: 29.0.50; Enabling pp-use-max-width dramatically slows down formatting of large sexps like org-persist--index Michael Eliachevitch
2023-01-12 11:27 ` Ihor Radchenko
2023-01-12 13:36 ` Eli Zaretskii
2023-01-12 16:19 ` Ihor Radchenko
2023-01-12 16:33 ` Visuwesh
2023-01-12 16:39 ` Eli Zaretskii
[not found] ` <87cz7j8j5o.fsf@posteo.de>
2023-01-12 23:02 ` bug#58687: Fwd: " Michael Eliachevitch
2023-01-13 8:42 ` Eli Zaretskii [this message]
2023-01-13 9:28 ` Ihor Radchenko
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=83o7r2akqf.fsf@gnu.org \
--to=eliz@gnu.org \
--cc=58687@debbugs.gnu.org \
--cc=m.eliachevitch@posteo.de \
--cc=yantar92@posteo.net \
/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 public inbox
https://git.savannah.gnu.org/cgit/emacs.git
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).