From: Bastien <bzg@gnu.org>
To: "Dominik, Carsten" <C.Dominik@uva.nl>
Cc: Org Mode List <emacs-orgmode@gnu.org>
Subject: Re: Sticky Agenda buffer: Announcement and request for testing
Date: Tue, 03 Apr 2012 07:33:40 +0200 [thread overview]
Message-ID: <87mx6ts7kb.fsf@gnu.org> (raw)
In-Reply-To: <65860CF1-3D9B-497B-8EF7-AA7E87B28BEE@uva.nl> (Carsten Dominik's message of "Sun, 11 Mar 2012 12:48:16 +0000")
Hi Carsten and Max,
"Dominik, Carsten" <C.Dominik@uva.nl> writes:
> already in Januar, Max Mikhanosha had published the first
> version of his code to implement multiple agenda buffers. I have
> worked with him over the last few weeks, and we think that
> it is now quite stable.
I've been trying the agenda-sticky branch a few times now and I love
this feature -- thanks a lot!
One request: I often use buffer restrictions in combination with agenda
views. For example, I restrict to a first-level tree then run my daily
agenda on that tree.
In this case, using sticky agenda is a bit confusing because I expect
a completely different agenda view while using the same agenda key (none
of the items in a tree are part of another subtree.)
Could we have an option allowing a set of rules (or a set of agenda
views) for which we want the rebuilding to be done automatically? I
would turn on this for my daily agenda views.
Thanks,
--
Bastien
next prev parent reply other threads:[~2012-04-03 5:32 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-11 12:48 Sticky Agenda buffer: Announcement and request for testing Dominik, Carsten
2012-03-13 17:30 ` Manuel Hermenegildo
2012-03-13 19:21 ` Samuel Wales
2012-04-03 5:37 ` Bastien
2012-03-14 15:54 ` Rainer Stengele
2012-03-14 18:12 ` Max Mikhanosha
2012-03-22 9:57 ` Rainer Stengele
2012-03-22 10:12 ` Bastien
2012-03-22 11:04 ` Rainer Stengele
2012-03-27 11:46 ` Martyn Jago
2012-04-03 5:33 ` Bastien [this message]
2012-04-03 6:58 ` Carsten Dominik
2012-04-03 7:06 ` Bastien
2012-04-03 7:09 ` Dominik, Carsten
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=87mx6ts7kb.fsf@gnu.org \
--to=bzg@gnu.org \
--cc=C.Dominik@uva.nl \
--cc=emacs-orgmode@gnu.org \
/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
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
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).