From: Robert Thorpe <rt@robertthorpeconsulting.com>
To: Jean Louis <bugs@gnu.support>
Cc: 44610@debbugs.gnu.org
Subject: bug#44610: 27.1; Keyboard Macro Performance Problem
Date: Wed, 18 Nov 2020 05:22:18 +0000 [thread overview]
Message-ID: <875z63b5o5.fsf@robertthorpeconsulting.com> (raw)
In-Reply-To: <X7K79yOuIuVCGGZB@protected.rcdrun.com> (message from Jean Louis on Mon, 16 Nov 2020 20:50:47 +0300)
Jean Louis <bugs@gnu.support> writes:
> * Eli Zaretskii <eliz@gnu.org> [2020-11-16 19:23]:
>> > From: Robert Thorpe <rt@robertthorpeconsulting.com>
>> > Cc: 44610@debbugs.gnu.org
>> > Date: Sun, 15 Nov 2020 23:44:32 +0000
>> >
>> > > I suggest to produce and present a profile of this. Invoke this macro
>> > > after "M-x profiler-start RET RET", then "M-x profiler-report RET",
>> > > expand the profile fully by "C-u RET" on the top line, and post the
>> > > result here. That should give some clues.
>> >
>> > Here is the report. I did it in Python-mode using Emacs -Q on Emacs
>> > 27.1. My machine is a Dell 14-3480. The profile I've got seems to be a
>> > bit different to the one Jean Louis got.
>
> I was in empty buffer with python-mode. Maybe you had some python code
> already inside? I did not have.
In my buffer I did what I described in the bug report. I had the string:
ffffffffffffffffffff (pppppppppppppppppppp);
Copied 300 times. That way the macro could operate on it.
BR,
Robert Thorpe
prev parent reply other threads:[~2020-11-18 5:22 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-11-13 2:51 bug#44610: 27.1; Keyboard Macro Performance Problem Robert Thorpe
2020-11-13 8:55 ` Jean Louis
2020-11-14 14:26 ` Eli Zaretskii
2020-11-14 16:03 ` Jean Louis
2020-11-14 16:24 ` Eli Zaretskii
2020-11-14 16:50 ` Eli Zaretskii
2020-11-15 23:44 ` Robert Thorpe
2020-11-16 16:23 ` Eli Zaretskii
2020-11-16 17:50 ` Jean Louis
2020-11-18 5:22 ` Robert Thorpe [this message]
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=875z63b5o5.fsf@robertthorpeconsulting.com \
--to=rt@robertthorpeconsulting.com \
--cc=44610@debbugs.gnu.org \
--cc=bugs@gnu.support \
/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.