Re: [O] [PATCH 2/3] Honour existing restrictions when clocking in from the agenda

[Bernt Hansen]

"Sebastien Vauban"
<address@hidden> writes:

> 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.

Hi Seb,

These patches were created by me back in December and recently applied
by Bastien on Jan 11th so that's probably when the problem showed up.  I
saw the initial report about this alignment problem on the mailing list
when my gmane access came back but I couldn't reproduce it with my setup
(using org-indent-mode, but I didn't try very hard at the time) so I
just assumed incorrectly that this was caused by later commits I hadn't
pulled yet.

The 4 patches really all go in the same topic.  There are still other
problems with this series and right now I'm leaning towards dropping
them completely.  There are lots of places in the agenda where things
seem to go wrong if the org file restriction is retained.

Regards,
Bernt