On Saturday, 17 Jun 2017 at 16:39, Uwe Brauer wrote:
>> On Friday, 16 Jun 2017 at 21:05, Uwe Brauer wrote:
>> [...]
>
>
>> The v c sequence invokes the clock checking code. It has nothing to do
>> with timestamps but looks instead for gaps and overlaps in your
>> clocking. If
> On Friday, 16 Jun 2017 at 21:05, Uwe Brauer wrote:
> [...]
> The v c sequence invokes the clock checking code. It has nothing to do
> with timestamps but looks instead for gaps and overlaps in your
> clocking. If you clock those projects, you will have the information
> tha
On Friday, 16 Jun 2017 at 21:05, Uwe Brauer wrote:
[...]
> Then I use org-agenda and
> v c
>
> But nothing is really done. I don't see any effect of visualizing the
> conflicting date Monday 8:30-9:30
>
> What do I miss?
The v c sequence invokes the clock checking code. It has nothing to do
wi
Hi
Just to test I have the following entry in my diary
Mon 8:30-9:30 Project 1
Tue 8:30-9:30 Other data
Mon 8:30-9:30 Project 2
Then I use org-agenda and
v c
But nothing is really done. I don't see any effect of visualizing the
conflicting date Monday 8:30-9:30
What do I miss?
