Hi Ag, Ag Ibragimov <agzam.ibragi...@gmail.com> writes:
> While going through the source code, I've noticed that org-agenda-list > scans all the files in org-agenda-files and processes all Org items > those files contain. > > However, it seems when org-agenda-max-entries or org-agenda-max-todos > are not nil, it still processes every entry, and only after building > the agenda it reduces the number of items in the list. It's okay, but > if you have lots of files and tons of entries, it seems to be waste of > time and resources. Yes, agreed. `org-agenda-max-entries' and `org-agenda-max-entries' are less useful when the limitation is done *at the end* as it is now (my bad, as I implemented this). I would welcome a patch that take org-agenda-max-* variables into account right after the list of agenda items has been collected and just *before* any other filtering happens. Let me know if this is something you can explore. Thanks!
