emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Luca Ferrari <fluca1978@gmail.com>
To: Ihor Radchenko <yantar92@gmail.com>
Cc: emacs-org list <emacs-orgmode@gnu.org>
Subject: Re: emacs really slow when inserting a new source code block
Date: Wed, 28 Sep 2022 14:55:45 +0200	[thread overview]
Message-ID: <CAKoxK+6S4urDKNjus38aHzQD81hGgKJRHFTimVJm-mA8EEv8Sw@mail.gmail.com> (raw)
In-Reply-To: <87h70tgddk.fsf@localhost>

On Tue, Sep 27, 2022 at 3:22 PM Ihor Radchenko <yantar92@gmail.com> wrote:
>
> This is strange.
> Did nothing happen after M-x profiler-report?
> Can you try again and check if *CPU-Profiler-Report ...* buffer exists
> in Emacs (... will be current date and time)?

No, there is no buffer named cpu nor memory nor something alike in the
buffer list.

Besides, I'm now more able to reproduce the original issue: I open one
of my perl-based org files, and it takes a lot, then I switch to
overview and it requires almost a minute to collapse all the headings.
Never seen nothing like this before.

Luca


  reply	other threads:[~2022-09-28 13:10 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-09-25 17:35 emacs really slow when inserting a new source code block Luca Ferrari
2022-09-26  4:42 ` Ihor Radchenko
2022-09-26 15:07   ` Luca Ferrari
2022-09-26 15:17     ` Ihor Radchenko
2022-09-27 12:42       ` Luca Ferrari
2022-09-27 13:23         ` Ihor Radchenko
2022-09-28 12:55           ` Luca Ferrari [this message]
2022-09-28 13:16             ` Ihor Radchenko
2022-09-28 14:15               ` Luca Ferrari
2022-09-28 14:21                 ` Luca Ferrari
2022-09-29  2:28                   ` Ihor Radchenko
2022-09-29 14:10                     ` Luca Ferrari
2022-09-29 14:19                       ` Ihor Radchenko
2022-10-05  6:03                         ` Luca Ferrari

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.orgmode.org/

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

  git send-email \
    --in-reply-to=CAKoxK+6S4urDKNjus38aHzQD81hGgKJRHFTimVJm-mA8EEv8Sw@mail.gmail.com \
    --to=fluca1978@gmail.com \
    --cc=emacs-orgmode@gnu.org \
    --cc=yantar92@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/org-mode.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).