From mboxrd@z Thu Jan 1 00:00:00 1970 From: Karl Voit Subject: Re: Toggle between active and inactive timestamp in CLOCK line does not make sense Date: Tue, 26 Jun 2012 17:26:43 +0200 Message-ID: <2012-06-26T17-11-59@devnull.Karl-Voit.at> References: <2012-06-26T12-47-32@devnull.Karl-Voit.at> <20120626140658.GA10119@boo.workgroup> Reply-To: news1142@Karl-Voit.at Mime-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 8bit Return-path: Received: from eggs.gnu.org ([208.118.235.92]:34034) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjXfZ-0000UP-1Z for emacs-orgmode@gnu.org; Tue, 26 Jun 2012 11:27:14 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1SjXfQ-0000ss-Uf for emacs-orgmode@gnu.org; Tue, 26 Jun 2012 11:27:08 -0400 Received: from plane.gmane.org ([80.91.229.3]:52470) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1SjXfQ-0000sO-O7 for emacs-orgmode@gnu.org; Tue, 26 Jun 2012 11:27:00 -0400 Received: from list by plane.gmane.org with local (Exim 4.69) (envelope-from ) id 1SjXfN-0007GM-EF for emacs-orgmode@gnu.org; Tue, 26 Jun 2012 17:26:57 +0200 Received: from mail.michael-prokop.at ([88.198.6.110]) by main.gmane.org with esmtp (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jun 2012 17:26:57 +0200 Received: from news1142 by mail.michael-prokop.at with local (Gmexim 0.1 (Debian)) id 1AlnuQ-0007hv-00 for ; Tue, 26 Jun 2012 17:26:57 +0200 List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: emacs-orgmode@gnu.org * Gregor Zattler wrote: > Hi Karl, Reiner, org-mode users and developers, > * Karl Voit [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. ... and this just because somebody is too lazy to put the cursor where it should go :-) (no offense!) -- Karl Voit