emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: [BUG] Re: How to trigger the clockcheck in an agenda view.
Date: Wed, 11 Sep 2013 12:24:23 +0200	[thread overview]
Message-ID: <868uz3bqqw.fsf@somewhere.org> (raw)
In-Reply-To: CANMKmeezct+YjYnJL7Hs1N_X4S=oaTCoMG5rym3MRGS+nMPvFg@mail.gmail.com

Hi Nicolas,

Nicolas Girard wrote:
> 2013/8/5 Sebastien Vauban <sva-news-D0wtAvR13HarG/iDocfnWg@public.gmane.org>:
>> 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 confirm that I can reproduce the bug you've spotted.

Great finding you've done there... This is the kind of obvious thing very
difficult to spot...

And, in fact, the extract I sent early of August wasn't working for me. Well,
the same version from a multi-block agenda view. This completely corroborates
your sayings...

> (I just borrowed your scissors to delimit my code, hope you don't mind ;-) )

These are not mine: just the default ones when pressing `C-c M-m' when
composing a message in Emacs!

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

Indeed, while G is good, B is not firing up the "clock check" as expected.

Best regards,

Sebastien Vauban

  reply	other threads:[~2013-09-11 10:24 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-12  8:06 How to trigger the clockcheck in an agenda view Rainer Stengele
2013-07-17 12:07 ` Rainer Stengele
2013-07-29  7:21   ` Rainer Stengele
2013-07-29  8:48     ` Sebastien Vauban
2013-07-31  7:25       ` Rainer Stengele
2013-08-04 20:32         ` Mike McLean
2013-08-05 20:43         ` Sebastien Vauban
2013-09-10 15:07           ` Nicolas Girard
2013-09-11 10:24             ` Sebastien Vauban [this message]
2013-09-27 13:00             ` Carsten Dominik
2014-11-20 12:51               ` Rainer Stengele
2014-11-25 17:02                 ` Rainer Stengele
2014-12-06 15:29                   ` Bernt Hansen
2014-12-07 14:21                     ` Rainer Stengele

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=868uz3bqqw.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).