I'd use use-package, treat org-agenda as separate package, defer its loading and declare org-agenda-files there. It should load the variable just before the agenda is loaded.
Alternatively I guess that you can exclude that file from your init file, and use add-to-list in org-agenda-mode-hookor any other convenient place you'll call before loading agenda-...
The solution I settled on was to remove the setting for org-agenda-files from my .emacs and instead to set org-agenda-files within some file local variables in the org-mode files that were actually relevant to the agenda. i.e. a block of code like this at the end of those files:
# Local Variables:
# eval: (setq org-agenda-files '("/-:somehost:somefile.org"))...
I found the answer by searching for variables with "agenda" and "clock" and "report" using Helm.
The variable org-agenda-clockreport-parameter-plist can be modified with the following
I modified the variable using Emacs' customize screen, but then I moved it from
custom.el to my own init.el, and this works for me:...
For starters, my suggestion would be to use DEADLINE: rather than SCHEDULED:. See The Org Manual: Deadlines and scheduling for an explanation of the distinction. Namely:
SCHEDULED Meaning: you are planning to start working on that task on
the given date.
DEADLINE Meaning: the task (most likely a TODO item, though not
necessarily) is supposed ...
You can accomplish this by defining a function such as my/org-agenda-insert-efforts that inserts the sum of the efforts next to the heading for a particular day after the agenda has been generated. The function only considers scheduled items for a particular day:
(defun my/org-agenda-calculate-efforts (limit)
"Sum the efforts of ...