From mboxrd@z Thu Jan 1 00:00:00 1970 From: Matthew Lundin Subject: Re: Trouble setting variables in custom agenda command Date: Thu, 04 Jun 2009 20:48:41 -0500 Message-ID: <871vpz5u2u.fsf@fastmail.fm> References: <20090527020507.GA5071@owl.prv.maya.com> <87my8puoa7.fsf@gollum.intra.norang.ca> <11098.1244067981@alphaville.usa.hp.com> <11277.1244069970@alphaville.usa.hp.com> <08FF8C08-A8CA-4DC9-B5C4-86240CA36B11@gmail.com> <20090604150600.GA1265@owl.prv.maya.com> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from mailman by lists.gnu.org with tmda-scanned (Exim 4.43) id 1MCOWr-00081f-0R for emacs-orgmode@gnu.org; Thu, 04 Jun 2009 21:47:33 -0400 Received: from exim by lists.gnu.org with spam-scanned (Exim 4.43) id 1MCOWm-0007ya-Bz for emacs-orgmode@gnu.org; Thu, 04 Jun 2009 21:47:32 -0400 Received: from [199.232.76.173] (port=51399 helo=monty-python.gnu.org) by lists.gnu.org with esmtp (Exim 4.43) id 1MCOWm-0007yS-6e for emacs-orgmode@gnu.org; Thu, 04 Jun 2009 21:47:28 -0400 Received: from out2.smtp.messagingengine.com ([66.111.4.26]:42574) by monty-python.gnu.org with esmtp (Exim 4.60) (envelope-from ) id 1MCOWk-0001oK-TA for emacs-orgmode@gnu.org; Thu, 04 Jun 2009 21:47:27 -0400 In-Reply-To: <20090604150600.GA1265@owl.prv.maya.com> (Christopher DeMarco's message of "Thu, 4 Jun 2009 11:06:00 -0400") List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Christopher DeMarco Cc: emacs org-mode mailing list Christopher DeMarco writes: > On Thu Jun 4 09:49:19 2009 +0200, Carsten Dominik wrote: > >> A block agenda has *two* places where options can be stored. >> One set of options for just the individual command, and one >> set for for the block as a whole. Things like >> org-agenda-start-with-column-view need to be set there, because >> they are only used in that final cleanup that happens in the >> second call to org-finalize-agenda, as Nick has described. > > Need to be set "where"? The options for the individual command or for > the whole block? I believe the second set of options (b below) -- i.e., the ones that come at the end of the agenda block command and apply to the block as a whole. --8<---------------cut here---------------start------------->8--- (setq org-agenda-custom-commands '(("c" "The Cycle" ((agenda "" ;; What follows is a) the first set of options. ;; They apply to for the agenda command above. ((org-agenda-ndays 1) (org-agenda-skip-function '(org-agenda-skip-entry-if 'notregexp "\\* TODO"))))) ;; What follows is b) the second set of options. ;; It is for the block as a whole. ;; If you had additional commands it would apply to them too. ((org-agenda-overriding-columns-format "%75ITEM %7Effort{:} %7CLOCKSUM{Total} %15TAGS %SCHEDULED") (org-agenda-view-columns-initially t) (org-agenda-start-with-log-mode t))))) --8<---------------cut here---------------end--------------->8--- Regards, Matt