From: Max Mikhanosha <max@openchat.com>
To: emacs-orgmode@gnu.org
Subject: Sticky agenda branch merged
Date: Mon, 16 Apr 2012 05:47:03 -0400 [thread overview]
Message-ID: <87aa2chuug.wl%max@openchat.com> (raw)
I had just pushed a merge of max-sticky-agenda branch to master, let
me know if there are any problems, also feel free to hack/iterate on
it, if you have question as to why something was done, I'll do my best
to answer.
In particular I just seen a new commit introducing filter on
categories, and org-agenda-filtered-by-top-category probably needs to
be included into local variable list to have it work per agenda
buffer.
Also the individual calls to org-todo-list and such, do not work right
with sticky agenda as there is nothing to catch the 'exit tag, that is
thrown by `org-prepare-agenda' when it finds cached buffer. I'm not
sure there is more elegant way of fixing it, other then wrapping all
the individual scanner pieces with (catch) blocks, that re-throw if
they had detected that they been called from (org-agenda) command
Regards,
Max
next reply other threads:[~2012-04-16 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 9:47 Max Mikhanosha [this message]
2012-04-16 17:44 ` Sticky agenda branch merged Tassilo Horn
2012-04-16 18:27 ` Charles Philip Chan
2012-04-16 22:59 ` Max Mikhanosha
2012-04-16 23:23 ` Charles Philip Chan
2012-04-17 6:14 ` Tassilo Horn
2012-04-17 10:09 ` Rainer Stengele
2012-04-17 12:29 ` Max Mikhanosha
2012-04-17 13:23 ` Rainer Stengele
2012-04-17 15:32 ` Max Mikhanosha
2012-04-17 15:58 ` Rainer Stengele
2012-04-17 16:28 ` BUG: Agenda clock related "v" for multi-block agendas Max Mikhanosha
2012-04-17 17:41 ` Sticky agenda branch merged Rainer Stengele
2012-04-17 19:02 ` Rainer Stengele
2012-04-17 19:35 ` Nick Dokos
2012-04-17 20:06 ` Rainer Stengele
2012-04-17 22:33 ` Bernt Hansen
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=87aa2chuug.wl%max@openchat.com \
--to=max@openchat.com \
--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).