all messages for Emacs-related lists mirrored at yhetil.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: Fri, 14 Feb 2020 18:17:32 +0200	[thread overview]
Message-ID: <83v9o9nnxf.fsf@gnu.org> (raw)
In-Reply-To: <CAAjt43gNDVd-gwg8cSO4KfbhZMABaBJ=8ytkovRt95NYABoHBQ@mail.gmail.com> (message from Ivan Oreshnikov on Fri, 14 Feb 2020 17:08:19 +0100)

> From: Ivan Oreshnikov <oreshnikov.ivan@gmail.com>
> Date: Fri, 14 Feb 2020 17:08:19 +0100
> Cc: 39598@debbugs.gnu.org
> 
> Sorry, didn't notice your first message (didn't expect such a quick response :).
> 
> Yes, my profile is very similar to yours:

It is.  Looks like python-nav--forward-sexp is indeed the main
culprit.  To narrow this down even more, I suggest to load python.el
(not .elc!) manually into a new Emacs session, then repeat the
experiment, and show the profile below python-nav--forward-sexp.  This
might point out the part of that function that takes the lion's share
of the run time.

Thanks.





  reply	other threads:[~2020-02-14 16:17 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 [this message]
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
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

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=83v9o9nnxf.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 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.