From: Rainer Stengele <rainer.stengele@online.de>
To: Brady Trainor <algebrat@uw.edu>
Cc: emacs-orgmode@gnu.org
Subject: Re: cannot get an agenda showing logged todos, scheduled todos and clockcheck items at the same time
Date: Tue, 18 Nov 2014 22:44:30 +0100 [thread overview]
Message-ID: <546BBDBE.9080007@online.de> (raw)
In-Reply-To: <87k32u2o89.fsf@uw.edu>
Am 17.11.2014 10:03, schrieb Brady Trainor:
> Hello,
>
> Rainer Stengele <rainer.stengele@online.de> writes:
>
>> (agenda "todays agenda"
>> (
>> (org-agenda-span 'day)
>> (org-agenda-log-mode 'clockcheck)
>> (org-agenda-start-with-log-mode t)
>> (org-agenda-overriding-header "Today's Agenda")))
> I am not using this, so I won't be able to test it but... I did google clockcheck and check some of your variables.
>
> If I execute M-x apropos RET org agenda log mode RET, it appears this is a command not a variable, at least in my org-mode version 8.2.10.
>
> A few lines down (in the apropos findings) I see `org-agenda-log-mode-items', which I think it should be a list, so for example
>
> #+BEGIN_SRC emacs-lisp
> (org-agenda-log-mode-items '(closed clock state))
> #+END_SRC
>
> Consider your thread http://thread.gmane.org/gmane.emacs.orgmode/74599 from July. There, Sebastien Vauban suggested the variable assignment
>
> #+BEGIN_SRC emacs-lisp
> (org-agenda-log-mode 'clockcheck)
> #+END_SRC
>
> Perhaps this is what you meant above. Or Mike McLean suggests,
>
> #+BEGIN_SRC emacs-lisp
> (org-agenda-show-log 'clockcheck)
> #+END_SRC
>
> Then, at the end of the thread, Carsten Dominick advises against using these, and suggest instead to use these in the global section of your custom command.
>
> #+BEGIN_SRC
> (org-agenda-start-with-log-mode 'clockcheck)
> (org-agenda-start-with-clockreport-mode t)
> #+END_SRC
>
> In summary, maybe you should have this:
>
> #+BEGIN_SRC emacs-lisp
> (setq org-agenda-custom-commands
> '(("Z" "todays agenda"
> ((agenda ""))
> ((org-agenda-span 'day)
> (org-agenda-start-with-log-mode 'clockcheck)
> (org-agenda-start-with-clockreport-mode t)
> (org-agenda-log-mode-items '(closed clock state))
> (org-agenda-overriding-header "Today's Agenda")))))
> #+END_SRC
>
> Further, I shifted some of the terms around. Note the `agenda' block usually takes the empty string, but it seems you gave it the name of the command.
>
> HTH
>
> --
> Brady
>
>> Thank you.
>> Regards, Rainer
Thanks Brady,
I tried what you suggested but same result: it only shows clockcheck entries without the scheduled todos.
I cannot get both to display at the same time.
Anybody have an idea?
Thank you,
Rainer
prev parent reply other threads:[~2014-11-18 21:44 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 8:18 cannot get an agenda showing logged todos, scheduled todos and clockcheck items at the same time Rainer Stengele
2014-11-17 9:03 ` Brady Trainor
2014-11-18 21:44 ` Rainer Stengele [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:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
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=546BBDBE.9080007@online.de \
--to=rainer.stengele@online.de \
--cc=algebrat@uw.edu \
--cc=emacs-orgmode@gnu.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* 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
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
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).