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: Re: [BUG] Re: Troubles with custom agenda commands
Date: Wed, 11 Sep 2013 13:19:30 +0200	[thread overview]
Message-ID: <86fvtba9ml.fsf@somewhere.org> (raw)
In-Reply-To: 86txhraabm.fsf_-_@somewhere.org

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	other threads:[~2013-09-11 11:19 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 12:02 Troubles with custom agenda commands Sebastien Vauban
2012-09-18  7:10 ` Bastien
2012-09-19 19:20   ` Sebastien Vauban
     [not found]     ` <804nmt95wa.fsf-oHC15RC7JGTNLxjTenLetw@public.gmane.org>
2013-09-11 11:04       ` [BUG] " Sebastien Vauban
2013-09-11 11:19         ` Sebastien Vauban [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=86fvtba9ml.fsf@somewhere.org \
    --to=sva-news-d0wtavr13harg/idocfnwg@public.gmane.org \
    --cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).