Thorsten Jolitz writes:
> ,-
> | M-: (org-timestamp-up 3)
> `-
The "3" here means 3 minutes, not "3 steps up", so the rounding
happens after minutes have been added.
> should change minutes
>
> - up 3 units when valus is (1 1)
> - up 15 units wh
Bastien writes:
> Hi Thorsten,
>
> Thorsten Jolitz writes:
>
>> 2. M-: (org-timestamp-up 3)
>>
>> results in:
>>
>> ,--
>> | ** Cafe <2014-01-23 Do 19:35>
>> `--
>>
>> 3. cross-check that the other units work by repeating 1 and 2 with
>>
Hi Thorsten,
Thorsten Jolitz writes:
> 2. M-: (org-timestamp-up 3)
>
> results in:
>
> ,--
> | ** Cafe <2014-01-23 Do 19:35>
> `--
>
> 3. cross-check that the other units work by repeating 1 and 2 with
>point on hour, month etc.
Yes, b
Bastien writes:
Hi Bastien,
> Thorsten Jolitz writes:
>
>> Bug or feature?
>>
>> Why is there this special handling of minutes? Evaluating
>>
>> ,-
>> | (org-timestamp-up 3)
>> `-
>>
>> with point on year, month, day, hour works as expected (3 units up),
Hi Thorsten,
Thorsten Jolitz writes:
> Bug or feature?
>
> Why is there this special handling of minutes? Evaluating
>
> ,-
> | (org-timestamp-up 3)
> `-
>
> with point on year, month, day, hour works as expected (3 units up), but
> not with point on minut
Bug or feature?
Why is there this special handling of minutes? Evaluating
,-
| (org-timestamp-up 3)
`-
with point on year, month, day, hour works as expected (3 units up), but
not with point on minute. There it's always a 1 unit change due to this
code sn
