dark.key8...@151e.ai writes:
> On Wed, Jan 24, 2024, at 23:02, Ihor Radchenko wrote:
>> What is the value of `default-directory' if you run the following from
>> Org git folder?
> ...
> in that case, it works, `default-directory' is the Org git folder,
> `load-path' has been correctly set and the
On Wed, Jan 24, 2024, at 23:02, Ihor Radchenko wrote:
> What is the value of `default-directory' if you run the following from
> Org git folder?
>
> emacs -Q --eval '(add-to-list '"'"'load-path (concat
> default-directory "lisp"))' --eval '(add-to-list '"'"'load-path (concat
> default-direct
dark.key8...@151e.ai writes:
> On Tue, Jan 23, 2024, at 03:57, Ihor Radchenko wrote:
>> May you post the output of
>
> There you go, I infer emacs is launched from $HOME since the two evals in the
> command launching emacs lead to `load-path' being prepended with "~/lisp" and
> "~/testing".
Tha
dark.key8...@151e.ai writes:
> make repro still can't load the correct org because make apparently
> launches emacs from my $HOME instead of the repo directory (I tested
> manually that `default-directory' is correct when calling emacs -Q) so
> I'm think make is reverting to $HOME when launching e
On Mon, Jan 22, 2024, at 20:05, Ihor Radchenko wrote:
> This is very strange. We try hard to use only GNU make machinery + Emacs
> there. May it help to remove local.mk from org git folder?
Ok, I didn't do that but recloned the repo manually (I was working from a
clone made by straight.el) and
dark.key8...@151e.ai writes:
> Side note about "make repro": it wouldn't load org from the repo.
> Trying to understand why, running "make autoloads", I was expecting
> (perhaps wrongly) that `org-version.el' and `org-loaddefs.el' would be
> generated in the repo directory/sub-directories but that
On Fri, Jan 19, 2024, at 23:15, Ihor Radchenko wrote:
> 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 shou
dark.key8...@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 bu
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.
--
dark.key8...@151e.ai writes:
> Please find attached.
Thanks!
> I found the profiler-reports harder to read because of the (native-compiled?)
> lambda that show up and harder to compare since the metric is relative with
> no absolute reference but well noted and will remember.
Yeah. For some r
On Fri, Jan 19, 2024, at 20:57, Ihor Radchenko wrote:
> May you please redo the benchmarks using
> 1. M-x profiler-start cpu
> 2. Run agenda
> 3. M-x profiler-report
> 4. M-x profiler-report-write-profile profile.el
> 5. Share two saved profiles, repeating the above steps with newer and
>ol
dark.key8...@151e.ai writes:
> I've been running 9.7 for a few weeks and I've noticed a slowdown in
> `org-agenda-redo'. I finally ran some benchmarks.
Thanks!
> I can reproduce it with a minimal org config (bare init.el with only
> straight.el and a short org config) with my full `org-agenda-fi
I've been running 9.7 for a few weeks and I've noticed a slowdown in
`org-agenda-redo'. I finally ran some benchmarks.
I can reproduce it with a minimal org config (bare init.el with only
straight.el and a short org config) with my full `org-agenda-files' (~450
files). In my regular conf, both
13 matches
Mail list logo
