From: Max Mikhanosha <max@openchat.com>
To: Rainer Stengele <rainer.stengele@online.de>
Cc: emacs-orgmode@gnu.org
Subject: BUG: Agenda clock related "v" for multi-block agendas
Date: Tue, 17 Apr 2012 12:28:39 -0400 [thread overview]
Message-ID: <87aa2a491k.wl%max@openchat.com> (raw)
In-Reply-To: <4F8D9323.6070309@online.de>
At Tue, 17 Apr 2012 17:58:27 +0200,
Rainer Stengele wrote:
> What I just found:
>
> being in a sticky agenda and trying "v r" I get this error which was not there before the merge:
> org-agenda-check-type: Not allowed in nil-type agenda buffers.
> Actually "v c" directly before entering "v r" gave results!
Investigating this showed it's not related to sticky agendas, but
uncovered the following bug. Clock related sub-functions of the "v"
key, have a check that they could only be done in the time related
agenda buffers, as opposite to the ones generated by C-c a t
For multi-block agendas, that include a an "agenda" block followed by
several "todo" blocks, you can only invoke "v c" or "v r" when point
is in the daily agenda block area, instead of tags or todo block area.
Interestingly enough the block separator line (the ============) has
agenda type text property of nil, so you only get the "type nil"
message when you do "v r" or "v c" with point on the separator line.
Regards,
Max
next prev parent reply other threads:[~2012-04-17 16:28 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-04-16 9:47 Sticky agenda branch merged Max Mikhanosha
2012-04-16 17:44 ` 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 ` Max Mikhanosha [this message]
2012-04-17 17:41 ` 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=87aa2a491k.wl%max@openchat.com \
--to=max@openchat.com \
--cc=emacs-orgmode@gnu.org \
--cc=rainer.stengele@online.de \
/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).