From: Rainer Stengele <rainer.stengele@online.de>
To: emacs-orgmode@gnu.org
Subject: Re: Sticky agenda branch merged
Date: Tue, 17 Apr 2012 17:58:27 +0200 [thread overview]
Message-ID: <4F8D9323.6070309@online.de> (raw)
In-Reply-To: <87bomq4bny.wl%max@openchat.com>
Hi Max,
I'll try later.
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!
Thanks,
Rainer
Am 17.04.2012 17:32, schrieb Max Mikhanosha:
> Hi Rainer,
>
> At Tue, 17 Apr 2012 15:23:00 +0200,
> Rainer Stengele wrote:
>>
>> Am 17.04.2012 14:29, schrieb Max Mikhanosha:
>>> At Tue, 17 Apr 2012 12:09:40 +0200,
>>> Rainer Stengele wrote:
>>>> Am 16.04.2012 11:47, schrieb Max Mikhanosha:
>>>>> 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
>>>> I see a strange behaviour when clocking in with C-c C-x C-i.
>>>> Sometimes (!) there is no new CLOCK: entry created.
>>>> The TODO state changes as expected, but no new CLOCK: line is created, even when clocking out.
>>>> Looks like this happens when the initial TODO state is set.
>>>>
>>>> Maybe I missed a change in the behaviour?
>>> Rainer, I can't reproduce this, can you give me a few more details?
>>>
>>> 1. Are you doing C-c C-x C-i from agenda, or from an Org File?
>>
>> from org file
>>
>>>
>>> 2. I don't understand the "TODO state changes as expected" part, I
>>> thought clock-in command has no effect on todo state, ie it simply
>>> adds CLOCK line to logbook drawer. Is there some extra configuration I
>>> need to change to enable this bit?
>>
>> I have set "org-clock-in-switch-to-state" to "INARBEIT" state in my state sequence
>>
>> #+SEQ_TODO: TODO INARBEIT WARTEN | MOVED DONE CANCELED DELEGATED
>>
>> As soon as I am in state "INARBEIT" and doing a clockin, the CLOCK: line appears.
>>>
>>> 3. Are sticky agendas enabled?
>>
>> YES!
>>>
>>> 4. If its from agenda, and its sticky, is it freshly generated, or was
>>> it refreshed with "g" or "r" key?
>> it is not from agenda
>>>
>>> 5. If its from sticky agenda, can you reproduce it without enabling sticky agendas?
>> Let me see: no, problem occurs with or without sticky agendas
>>>
>
> So far this looks to me as its unrelated to sticky changes, could you
> by any chance try commit 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0
> which is 1 before sticky merge , and see if same scenario is broken
> there?
>
> The git commands to do it (ignore if your git-fu is strong)
>
> git checkout 3bd1c2e9bff539c94f92f1ec919f8f0f1640f8c0
> ... test ..
> git checkout master
> ... back to normal ..
>
> Regards,
> Max
>
>
>
next prev parent reply other threads:[~2012-04-17 15:58 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 [this message]
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=4F8D9323.6070309@online.de \
--to=rainer.stengele@online.de \
--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).