Re: Exporting with block agenda

[Carsten Dominik <dominik@uva.nl>]

You are completely right.  This is a bug in Org-mode.

- Carsten

On Jul 22, 2008, at 11:53 AM, Jan Seeger wrote:

> At Tue, 22 Jul 2008 11:09:22 -0700,
> Carsten Dominik wrote:
>>
>>
>> On Jul 22, 2008, at 10:49 AM, Jan Seeger wrote:
>>> 	  (setq org-agenda-custom-commands '(
>>> 	  							   ("c" ""
>>> 	  								((todo "NEXT|TODO") (agenda))
>>> 	  								((org-agenda-with-colors nil)
>>> 	  								 (ps-font-size '(8 . 8))
>>> 	  								 (org-agenda-compact-blocks t)
>>> 	  								 (ps-landscape-mode t)
>>> 	  								 (ps-number-of-columns 2)
>>> 	  								 )
>>> 	  								("/tmp/todo-list.ps")
>>> 	  								)
>>> 	  	  ))
>> The setting is wrong.  Parameters in org-agenda-custom-commands are
>> identified by
>> position, and your file list is seen as an attempt to set options
>> (variables)
>> for the command set.  You need nil there.
>>
>> Can you identify a point in the documentation that made you assume  
>> you
>> could write things a you did?
>
> Quote from C-h v org-agenda-custom-commands:
>
>> You can also define a set of commands, to create a composite agenda  
>> buffer.
>> In this case, an entry looks like this:
>>
>>   (key desc (cmd1 cmd2 ...) general-settings-for-whole-set files)
>
> This looks to me as if only four elements where needed: Key,
> description, list of lists of commands (agenda,alltodo etc), settings
> and filenames.
>
> Regards,
> Jan
> --
> Warning! Erwin Schrödinger will kill you like a cat in a box.
> Maybe.
>
>
> _______________________________________________
> Emacs-orgmode mailing list
> Remember: use `Reply All' to send replies to the list.
> Emacs-orgmode@gnu.org
> http://lists.gnu.org/mailman/listinfo/emacs-orgmode