2013/8/5 Sebastien Vauban <sva-n...@mygooglest.com>:
>
> Except the above, I definitely don't understand why it wouldn't work for you.
> Can you reproduce the problem with a minimal Emacs config file (adding the
> require of `org' and `org-agenda' before)?
>
I think I understand why Rainer has a problem.
According to the docstring from `org-agenda-custom-commands', there
are two acceptable syntaxes for defining a command:
- the "simple" one : (key desc type match settings files)
- and the "complex" or "composite" one : (key desc (cmd1 cmd2 ...)
general-settings-for-whole-set files).
Now, the following code defines two commands, who are functionally
identical, but syntactically different. The first one uses the "simple"
syntax, and the second one, the "complex" syntax.
If you evaluate the code and trigger the agenda, you'll see that the
first command *doesn't* work as expected, while the second works.
(I just borrowed your scissors to delimit my code, hope you don't mind ;-) )
--8<---------------cut here---------------start------------->8---
(setq org-agenda-custom-commands nil)
(setq org-agenda-custom-commands
(append
org-agenda-custom-commands '(
("G" "Good: Clock Review"
((agenda ""
((org-agenda-show-log 'clockcheck)
(org-agenda-clockreport-mode t)))))
("B" "Bad: Clock Review"
agenda ""
((org-agenda-show-log 'clockcheck)
(org-agenda-clockreport-mode t))))))
--8<---------------cut here---------------end--------------->8---
