From: Carsten Dominik <firstname.lastname@example.org> To: Max Mikhanosha <email@example.com> Cc: firstname.lastname@example.org Subject: Re: Multiple agenda buffers at email@example.com:7max/org-mode.git Date: Thu, 26 Jan 2012 11:35:05 +0000 [thread overview] Message-ID: <500FE03E-B59F-4742-B042-353D892F9561@gmail.com> (raw) In-Reply-To: <firstname.lastname@example.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. > > 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. > > 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 > > At Thu, 26 Jan 2012 09:50:22 +0000, Carsten Dominik wrote: >> >> Hi Max, >> >> 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... >> >> Cheers >> >> - Carsten >> >> On 25.1.2012, at 21:45, Max Mikhanosha wrote: >> >>> I had put my initial implementation of multiple agenda buffers and >>> sticky agenda support on email@example.com:7max/org-mode.git branch >>> multiple-agenda-buffers. >>> >>> To enable, use M-x org-toggle-sticky-agenda >>> >>> 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' >>> >>> For example: >>> >>> (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*"))))) >>> >>> >>> 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. >>> >>> This allows user to have many "mini-agendas" and switch between them >>> rapidly >>> >>> 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. >>> >>> Regards >>> Max >> >
next prev parent reply other threads:[~2012-01-26 11:35 UTC|newest] Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top 2012-01-25 21:45 Max Mikhanosha 2012-01-26 9:50 ` Carsten Dominik 2012-01-26 11:17 ` Max Mikhanosha 2012-01-26 11:35 ` Carsten Dominik [this message] 2012-01-26 11:39 ` Max Mikhanosha 2012-01-26 15:10 ` Max Mikhanosha
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=500FE03E-B59F-4742-B042-353D892F9561@gmail.com \ --firstname.lastname@example.org \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: Multiple agenda buffers at email@example.com:7max/org-mode.git' \ /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
Code repositories for project(s) associated with this 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).