From: Ihor Radchenko <yantar92@posteo.net>
To: dark.key8799@151e.ai
Cc: emacs-orgmode@gnu.org
Subject: Re: Slowness of org-agenda-redo in org 9.7 vs 9.6.7
Date: Fri, 19 Jan 2024 15:15:25 +0000 [thread overview]
Message-ID: <87cytx73si.fsf@localhost> (raw)
In-Reply-To: <54c5f233-7376-4657-bcb1-8b47e1620772@app.fastmail.com>
dark.key8799@151e.ai writes:
> On Fri, Jan 19, 2024, at 22:00, Ihor Radchenko wrote:
>> May you open org-agenda.el and org-element.el and M-x eval-buffer in
>> these two files before generating the report? It should make the results
>> more readable.
>
> There you go, there's still some lambdas but more of the calls are explicit.
Thanks!
I think that the missing lambdas should come from org.el.
So, may you M-x eval-buffer org-agenda.el, org-element.el, and org.el.
And do the same in Org 9.6. (there are also cryptic lambdas there in the
profile)
(In theory, you should not need to do this M-x eval-buffer trick if you
run Org mode from "make repro" command line in the git repo. Not sure if
it is easier for you or not)
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-01-19 15:13 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-19 10:35 Slowness of org-agenda-redo in org 9.7 vs 9.6.7 dark.key8799
2024-01-19 12:57 ` Ihor Radchenko
2024-01-19 13:49 ` dark.key8799
2024-01-19 14:00 ` Ihor Radchenko
2024-01-19 14:50 ` dark.key8799
2024-01-19 15:15 ` Ihor Radchenko [this message]
2024-01-22 6:09 ` dark.key8799
2024-01-22 12:05 ` Ihor Radchenko
2024-01-22 15:36 ` dark.key8799
2024-01-22 19:57 ` Ihor Radchenko
2024-01-23 2:35 ` dark.key8799
2024-01-24 15:02 ` Ihor Radchenko
2024-01-24 15:59 ` dark.key8799
2024-01-24 16:12 ` Ihor Radchenko
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=87cytx73si.fsf@localhost \
--to=yantar92@posteo.net \
--cc=dark.key8799@151e.ai \
--cc=emacs-orgmode@gnu.org \
/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).