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: Mon, 26 Sep 2022 17:07:42 +0200 [thread overview]
Message-ID: <CAKoxK+45V85RbXLRbe+DnHfQbPuDBcSB7Qsf18yXE9cjGOnmvA@mail.gmail.com> (raw)
In-Reply-To: <871qry7nmg.fsf@localhost>
On Mon, Sep 26, 2022 at 6:41 AM Ihor Radchenko <yantar92@gmail.com> wrote:
> Thanks for reporting!
> May you
> 1. M-x profiler-start <RET> cpu <RET>
> 2. Move/paste/edit your source block
> 3. M-x profiler-report <RET>
> 4. M-x profiler-report-write-profile and share the resulting file here
Apparently I'm not able to get the profiler report written.
However, I discovered that, for instance, when I'm editing a piece of
code with regexp Emacs seems to suffer, at least it is the only
chances I had today to get it slower.
The messages buffer does not help very much:
CPU and memory profiler started
End of ‘m/ ... /’ string/RE not found: (scan-error Unbalanced parentheses 74 82)
Auto-saving...done
CPU and memory profiler stopped
profiler-write-profile: Wrong type argument: arrayp, nil
As you can see, I cannot save the profiler report, neither by placing
a filename, nor leaving it to save in the current directory of the
file I'm editing.
Oh, I also tried to disable flyspell, but it seems to me it gets
re-enabled for the source code block I'm within (but it's just a
feeling).
Any idea?
Luca
next prev parent reply other threads:[~2022-09-26 15:20 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 [this message]
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
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+45V85RbXLRbe+DnHfQbPuDBcSB7Qsf18yXE9cjGOnmvA@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).