unofficial mirror of bug-gnu-emacs@gnu.org 
 help / color / mirror / code / Atom feed
From: Eli Zaretskii <eliz@gnu.org>
To: Ivan Oreshnikov <oreshnikov.ivan@gmail.com>
Cc: 39598@debbugs.gnu.org
Subject: bug#39598: 26.3; Emacs is extremely unresponsive on a trivial python file
Date: Sat, 15 Feb 2020 21:22:53 +0200	[thread overview]
Message-ID: <83zhdjmz8y.fsf@gnu.org> (raw)
In-Reply-To: <CAAjt43jHUdxteGMOLYtv6VoDOG6pZERfttm3Pd+sDD-Hvmotqg@mail.gmail.com> (message from Ivan Oreshnikov on Sat, 15 Feb 2020 19:49:37 +0100)

> From: Ivan Oreshnikov <oreshnikov.ivan@gmail.com>
> Date: Sat, 15 Feb 2020 19:49:37 +0100
> Cc: 39598@debbugs.gnu.org
> 
> > What is/are the real-life use case(s) where such long series of strings causes slowdown?
> 
> This is an intermediate state of python buffer when I am trying to build a large-ish dictionary with lists of strings
> as a value.

Why do you need that intermediate buffer to be in Python mode?

> What I find a bit weird is that it only happens to a long series of bare strings. If I construct an equally long
> proper python list of strings I don't see this behavior.

I guess because the code is tuned to support valid Python code, not
something that shouldn't happen in Python sources?





  reply	other threads:[~2020-02-15 19:22 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-02-14 10:48 bug#39598: 26.3; Emacs is extremely unresponsive on a trivial python file Ivan Oreshnikov
2020-02-14 13:35 ` Eli Zaretskii
2020-02-14 13:50   ` Eli Zaretskii
2020-02-14 16:08     ` Ivan Oreshnikov
2020-02-14 16:17       ` Eli Zaretskii
2020-02-14 16:31         ` Ivan Oreshnikov
2020-02-15  8:05           ` Eli Zaretskii
2020-02-15 18:49             ` Ivan Oreshnikov
2020-02-15 19:22               ` Eli Zaretskii [this message]
2020-02-15 19:31                 ` Ivan Oreshnikov
2020-03-13  3:00             ` Noam Postavsky
2020-09-20  8:47               ` Lars Ingebrigtsen

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=83zhdjmz8y.fsf@gnu.org \
    --to=eliz@gnu.org \
    --cc=39598@debbugs.gnu.org \
    --cc=oreshnikov.ivan@gmail.com \
    /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).