From mboxrd@z Thu Jan 1 00:00:00 1970 From: Carsten Dominik Subject: Re: Multiple agenda buffers at git@github.com:7max/org-mode.git Date: Thu, 26 Jan 2012 11:35:05 +0000 Message-ID: <500FE03E-B59F-4742-B042-353D892F9561@gmail.com> References: <87boprzcak.wl%max@openchat.com> <1CBFA95D-2D35-4BB0-92B1-94E5900DAA6C@gmail.com> <878vkuzp9i.wl%max@openchat.com> Mime-Version: 1.0 (Apple Message framework v1084) Content-Type: text/plain; charset=us-ascii Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([140.186.70.92]:51906) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RqNbq-0004Wm-0V for emacs-orgmode@gnu.org; Thu, 26 Jan 2012 06:35:23 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1RqNbj-0008TZ-AK for emacs-orgmode@gnu.org; Thu, 26 Jan 2012 06:35:17 -0500 Received: from mail-we0-f169.google.com ([74.125.82.169]:53882) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1RqNbi-0008TI-TU for emacs-orgmode@gnu.org; Thu, 26 Jan 2012 06:35:11 -0500 Received: by wera13 with SMTP id a13so379522wer.0 for ; Thu, 26 Jan 2012 03:35:10 -0800 (PST) In-Reply-To: <878vkuzp9i.wl%max@openchat.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Max Mikhanosha Cc: emacs-orgmode@gnu.org On 26.1.2012, at 11:17, Max Mikhanosha wrote: > I realize that I may have too many, my initial approach was to start > with some obvious one, then test and keep adding to the list. >=20 > But the bugs that shows up are hard to reproduce, and subtle, and it > was slow going, and I was sure I'm missing some. >=20 > So I went the other direction, and made a list of vars by grepping > org-agenda.el for "(defvar ....", and tested again, and it was easier > to eliminate the variables from the list, since any variables that > caused problems usually throw error (due to global value being NIL), > instead of doing something subtly wrong that is hard to notice. OK, I will go through that list... - Carsten >=20 > At Thu, 26 Jan 2012 09:50:22 +0000, Carsten Dominik wrote: >>=20 >> Hi Max, >>=20 >> how did you select the variables that should become buffer-local? >> You might have too many in your list, for example = org-last-heading-marker... >>=20 >> Cheers >>=20 >> - Carsten >>=20 >> On 25.1.2012, at 21:45, Max Mikhanosha wrote: >>=20 >>> I had put my initial implementation of multiple agenda buffers and >>> sticky agenda support on git@github.com:7max/org-mode.git branch >>> multiple-agenda-buffers. >>>=20 >>> To enable, use M-x org-toggle-sticky-agenda >>>=20 >>> In order to take full advantage of the sticky agenda, you need to = give >>> your various agendas different buffer names, you can do it by >>> including `org-agenda-buffer-name' into the list of bound variables = in >>> `org-agenda-custom-commands' >>>=20 >>> For example: >>>=20 >>> (setq org-agenda-custom-commands >>> '(("a" "Agenda and NEXT (priority)" >>> ((agenda "" >>> ((org-agenda-span 'day))) >>> (tags-todo "/!NEXT" >>> ((org-agenda-overriding-header "Next Tasks") >>> (org-agenda-tags-todo-honor-ignore-options t) >>> (org-agenda-todo-ignore-scheduled t) >>> (org-agenda-todo-ignore-deadlines t) >>> (org-tags-match-list-sublevels t) >>> (org-agenda-sorting-strategy >>> '(priority-down category-keep))))) >>> ((org-agenda-buffer-name "*Agenda*"))) >>> ("t" "TODO entries" >>> todo "" >>> ((org-agenda-buffer-name "*Todo List*"))))) >>>=20 >>>=20 >>> When sticky agenda is enabled, most of org-agenda Emacs variables >>> become buffer local, and org-agenda-quit is changed to bury the = buffer >>> instead of killing it. Correspondingly org-agenda will show = previously >>> buried buffer if it exists, instead of re-generating it. >>>=20 >>> This allows user to have many "mini-agendas" and switch between them >>> rapidly >>>=20 >>> I would appreciate any bug-reports about things not working, and of >>> course patches or fixes for them. The most likely cause of any >>> breakage is that `org-agenda-local-vars' list needs adjusting and/or >>> fixing. >>>=20 >>> Regards >>> Max >>=20 >=20