From: Marcelo de Moraes Serpa <firstname.lastname@example.org>
To: Marcelo de Moraes Serpa <email@example.com>,
Org Mode <firstname.lastname@example.org>,
Subject: Re: Frames and the agenda
Date: Mon, 27 Feb 2012 16:45:40 -0600 [thread overview]
Message-ID: <CACHMzOH7mt4TJCSVa6n8P82PWLihxedZbK-e=H5d+HRQiujMRA@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 2679 bytes --]
Hi Max, thanks for the reply.
That is amazing. Works like a charm - just what I needed.
This should definitely be merged back to the main org distribution!
On Fri, Feb 24, 2012 at 2:48 PM, Max Mikhanosha <email@example.com> wrote:
> Check out my multiple-agenda-buffers branch from
> Its designed exactly for that (multiple independent agenda buffers
> living together). to enable it use, M-x org-toggle-sticky-agenda
> You will have to set different agenda names for different agenda views
> in your org-agenda-custom-commands variable like so:
> (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)
> '(priority-down category-keep)))))
> ((org-agenda-buffer-name "*Agenda*")))
> ("t" "TODO entries"
> todo ""
> ((org-agenda-buffer-name "*Todo List*")))))
> Carsten suggested that this will eventually get merged, but I think
> people may be afraid, as it's a bit of a major change, converting most
> agenda related variables to buffer local, and at least initially had a
> several bugs, which took me a few weeks to catch and fix.
> But I've been running on this branch for a month+, and quality of
> my org-moding had greatly improved, since now all my agendas pop-out
> immediately instead of rebuilding for several seconds.
> At Fri, 24 Feb 2012 12:38:39 -0600,
> Marcelo de Moraes Serpa wrote:
> > Hey guys,
> > So, I would like to keep a sort of dashboard in a osx virtual desktop -
> basically having emacs frames with different todo lists
> > for reference at quick glance:
> > http://minus.com/mlgjv21R4
> > The problem is that the agenda is global to the emacs instance and won't
> allow me to show a filter view in one frame and another
> > in the other (i.e: One frame showing all my personal TODOs and the other
> showing all TODOs related to my job.).
> > I could have those lists in separate files, but my configuration now has
> all todos in a big gtd.org file.
> > Is there a way to have differente filters in different frames? If not,
> any thoughts on how I could accomplish this idea?
> > Thanks,
> > Marcelo.
[-- Attachment #2: Type: text/html, Size: 3565 bytes --]
next prev parent reply other threads:[~2012-02-27 22:45 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-02-24 18:38 Frames and the agenda Marcelo de Moraes Serpa
2012-02-24 20:48 ` Max Mikhanosha
2012-02-27 22:45 ` Marcelo de Moraes Serpa [this message]
2012-02-28 0:52 ` Marcelo de Moraes Serpa
2012-02-28 1:44 ` Nick Dokos
2012-02-28 9:49 ` Max Mikhanosha
2012-02-28 16:55 ` Marcelo de Moraes Serpa
2012-02-28 16:57 ` Marcelo de Moraes Serpa
2012-02-29 17:55 ` Rebased to the latest tip Max Mikhanosha
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).