Re: Toggle between active and inactive timestamp in CLOCK line does not make sense

[Karl Voit <devnull@Karl-Voit.at>]

* Gregor Zattler <telegraph@gmx.net> wrote:
> Hi Karl, Reiner, org-mode users and developers,
> * Karl Voit <devnull@Karl-Voit.at> [26. Jun. 2012]:
>> You might be right with «Toggle between active and inactive
>> timestamp in CLOCK line does not make sense» but I do think that
>> «the toggle mechanism to change timestamp type behaves consistently
>> everywhere» is more important here.
>
> But org-mode already has context-sensitive key bindings in
> various places, especially C-c C-c.  Why is this different?

Because it is not obvious that S-up/down is deactivated only in a
CLOCK line on timestamps. At least for me.

C-c C-c is consistent on its places. It is obvious that when you are
using C-c C-c in a table, it is unlikely that this action results in
adding tags as it does when invoked on a heading line. For example.

For the sake of being consistent, S-up/down should toggle the type
when invoked on a bracket of *every* timestamp. And not "it toggles
the timestamp type *except* in following cases ...".

I could imagine justified a discussion on that topic with a good
reason. But the only reason Reiner gave was that he does not want to
put his cursor on the (consistent) correct spot. In my opinion this
argument is is to weak to throw away consistency.

But I might be overruled or convinced by a lot of other people
arguing for the same change. I do not use clocking by my own (so
far) and therefore I really do not care if timestamp toggling
behaves differently when being in a CLOCK line. But I am concerned
by the general tendency that would start, when Org-mode becomes
indeterministic to the users on other places as well. <exaggeration>
... and this just because somebody is too lazy to put the cursor
where it should go </exaggeration> :-) (no offense!)

-- 
Karl Voit