From: "Sebastien Vauban" <wxhgmqzgwmuf-geNee64TY+gS+FvcfC7Uqw@public.gmane.org>
To: emacs-orgmode-mXXj517/zsQ@public.gmane.org
Subject: Re: [PATCH 2/3] Honour existing restrictions when clocking in from the agenda
Date: Thu, 19 Jan 2012 16:47:29 +0100 [thread overview]
Message-ID: <80hazrwv72.fsf@somewhere.org> (raw)
In-Reply-To: 87fwfb690d.fsf@norang.ca
Hi Bernt,
Bernt Hansen wrote:
> Eeek!
>
> I'm not running into this (as far as I know) in my current setup but I
> vote we just revert the clocking restriction patches. There are other
> unresolved issues with these patches that I've seen and don't currently
> have a fix for.
>
> Please revert the following commits (again). Sorry :(
>
> - 7a73e15 (Remove file restrictions when generating clock report data, 2012-01-09)
> - e8f93a75 (Honour existing restrictions when visiting tasks from the agenda, 2011-12-30)
> - c41a6f5 (Honour existing restrictions when clocking in from the agenda, 2011-12-30)
> - a0a26cd (Honour existing restrictions when regenerating the agenda, 2011-12-30)
FYI, I have the (subjective) impression that the below bug just came up a
couple of days ago. I would say less than one calendar week. But I may be
wrong.
>> After clocking in from the agenda -- (org-agenda-clock-in) -- the file
>> looks like this:
>>
>> * A headline
>> SCHEDULED: <2012-01-18 Wed +1d>
>> :LOGBOOK:
>> CLOCK: [2012-01-19 Thu 07:19]
>> CLOCK: [2012-01-18 Wed 20:10]--[2012-01-19 Thu 07:18] => 11:08
>> :END:
>> :PROPERTIES:
>> :HELLO: there
>> :END:
>> * And another
>> :PROPERTIES:
>> :NOW: and again
>> :END:
Best regards,
Seb
--
Sebastien Vauban
next prev parent reply other threads:[~2012-01-19 15:47 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 10:49 Honour existing restrictions if possible when visiting tasks from the agenda Bernt Hansen
2011-12-30 10:49 ` [PATCH 1/3] Honour existing restrictions when regenerating " Bernt Hansen
2011-12-30 10:49 ` [PATCH 2/3] Honour existing restrictions when clocking in from " Bernt Hansen
2012-01-19 13:43 ` Matt Lundin
2012-01-19 14:51 ` Bernt Hansen
2012-01-19 15:22 ` Bastien
2012-01-19 15:44 ` Bernt Hansen
2012-01-19 15:47 ` Sebastien Vauban [this message]
2012-01-19 16:11 ` Bastien
2012-01-19 18:05 ` Bernt Hansen
2011-12-30 10:49 ` [PATCH 3/3] Honour existing restrictions when visiting tasks " Bernt Hansen
2011-12-31 8:11 ` Honour existing restrictions if possible " Carsten Dominik
2011-12-31 14:12 ` 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=80hazrwv72.fsf@somewhere.org \
--to=wxhgmqzgwmuf-genee64ty+gs+fvcfc7uqw@public.gmane.org \
--cc=emacs-orgmode-mXXj517/zsQ@public.gmane.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).