emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Troubles with custom agenda commands
Date: Thu, 13 Sep 2012 14:02:17 +0200	[thread overview]
Message-ID: <80bohaf7w6.fsf@somewhere.org> (raw)

Hello,

Trying to write my own custom agenda commands, I face a couple of weird
behaviors.

#+begin_src emacs-lisp
  (add-to-list 'org-agenda-custom-commands
               '("S" "Summary Review"
                 ((agenda "")
                  (todo ""))
                 ((org-agenda-time-grid nil)
                  (org-agenda-clockreport-mode nil)
                  (org-deadline-warning-days 0))))
#+end_src

Having the above (which is correct, AFAICT from following the tutorial on
http://orgmode.org/worg/org-tutorials/org-custom-agenda-commands.html):

1. When getting to the agenda dispatcher (`C-c a'), I see:

--8<---------------cut here---------------start------------->8---
   S   Summary Review: set of 3 commands
--8<---------------cut here---------------end--------------->8---

  while I only have... 2 commands (`agenda' and `todo'). Why?

2. When firing it up (`C-c a' followed by `S'), I get the 2 blocks I was
   expecting, but also an error:

--8<---------------cut here---------------start------------->8---
   Buffer is read-only: #<buffer *Org Agenda(S)*>
--8<---------------cut here---------------end--------------->8---

Can you confirm this?

Best regards,
  Seb

-- 
Sebastien Vauban

             reply	other threads:[~2012-09-13 12:02 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-09-13 12:02 Sebastien Vauban [this message]
2012-09-18  7:10 ` Troubles with custom agenda commands 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

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=80bohaf7w6.fsf@somewhere.org \
    --to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@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).