emacs-orgmode
[Top][All Lists]
Advanced

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

Re: [O] [BUG] Re: Troubles with custom agenda commands


From: Sebastien Vauban
Subject: Re: [O] [BUG] Re: Troubles with custom agenda commands
Date: Wed, 11 Sep 2013 13:19:30 +0200
User-agent: Gnus/5.130006 (Ma Gnus v0.6) Emacs/24.3.50 (windows-nt)

Hi Bastien,

"Sebastien Vauban" wrote:
> "Sebastien Vauban" wrote:
>> Bastien wrote:
>>> "Sebastien Vauban" writes:
>>>
>>>> When getting to the agenda dispatcher (`C-c a'), I see:
>>>>
>>>>    S   Summary Review: set of 3 commands
>>>>
>>>>   while I only have... 2 commands (`agenda' and `todo'). Why?
>>>
>>> This is a bug, fixed.  Thanks for spotting this!
>>
>> Tested. Confirmed OK.
>
> The above problem is back with the following configuration (tested with
> "emacsĀ -Q"):
>
>     (add-to-list 'org-agenda-custom-commands
>                  '("C" "Clock Review"
>                    ((agenda ""
>                             ((org-agenda-clockreport-mode t)
>                              (org-agenda-overriding-header "Clocking Review")
>                              (org-agenda-show-log 'clockcheck)
>                              (org-agenda-span 'day))) t)))
>
> Org writes:
>
> C   Clock Review  : set of 2 commands
> n   Agenda and all TODO's: set of 2 commands
>
> while there is only 1 command to be run (the agenda view)!?

Please IGNORE IT!  This "bug" is due to a faulty placement of the parenthesis.

It should have been:

>     (add-to-list 'org-agenda-custom-commands
>                  '("C" "Clock Review"
>                    ((agenda ""
>                             ((org-agenda-clockreport-mode t)
>                              (org-agenda-overriding-header "Clocking Review")
>                              (org-agenda-show-log 'clockcheck)
>                              (org-agenda-span 'day))))) t)
                                                       ^^
Sorry for this false alarm.

> Note, surprisingly, 2 extra spaces before the ":", while they're not in the
> customized header string...

Best regards,
  Seb

-- 
Sebastien Vauban




reply via email to

[Prev in Thread] Current Thread [Next in Thread]