emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Bastien <bzg@gnu.org>
To: Ag Ibragimov <agzam.ibragimov@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: org-agenda-list should respect org-agenda-max-entries
Date: Mon, 26 Apr 2021 10:56:40 +0200	[thread overview]
Message-ID: <87lf95bf07.fsf@gnu.org> (raw)
In-Reply-To: <m2czwza6ya.fsf@gmail.com> (Ag Ibragimov's message of "Tue, 16 Feb 2021 18:11:57 -0600")

Hi Ag,

Ag Ibragimov <agzam.ibragimov@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!

      parent reply	other threads:[~2021-04-26  8:57 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-02-17  0:11 org-agenda-list should respect org-agenda-max-entries Ag Ibragimov
2021-02-21  6:32 ` Kyle Meyer
2021-04-26  8:56 ` Bastien [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:

  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=87lf95bf07.fsf@gnu.org \
    --to=bzg@gnu.org \
    --cc=agzam.ibragimov@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).