From mboxrd@z Thu Jan 1 00:00:00 1970 From: Gregor Zattler Subject: location of clocking out notes (was: Re: Release 9.0.5) Date: Sun, 26 Feb 2017 13:03:49 +0100 Message-ID: <20170226120349.kkqc7vq2smjlyvqb@len.workgroup> References: <8737fmxibv.fsf@gnu.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:55473) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1chxZF-0004i5-WE for emacs-orgmode@gnu.org; Sun, 26 Feb 2017 07:04:47 -0500 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1chxZC-00072h-Nm for emacs-orgmode@gnu.org; Sun, 26 Feb 2017 07:04:46 -0500 Received: from mout.gmx.net ([212.227.17.20]:63035) by eggs.gnu.org with esmtps (TLS1.0:DHE_RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1chxZC-000724-DV for emacs-orgmode@gnu.org; Sun, 26 Feb 2017 07:04:42 -0500 Received: from boo.workgroup ([84.189.137.23]) by mail.gmx.com (mrgmx103 [212.227.17.168]) with ESMTPSA (Nemesis) id 0MEo4s-1cWTNf4758-00G1ZC for ; Sun, 26 Feb 2017 13:04:38 +0100 Content-Disposition: inline In-Reply-To: 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" To: emacs-orgmode Hi Jorge, Bastien, org-mode developers, * Jorge Morais Neto [10. Feb. 2017]: > On 10 February 2017 at 11:53, Bastien wrote: >> Org 9.0.5, a minor bugfix release, is out. > In Org 9.0.5, clock out notes are again stored below the corresponding > clock line, restoring the behavior of an earlier release. There were > interim releases, up to 9.0.4, that stored the clock out notes /above/ > the clock line. Is there a consensus now where the clocking out notes should go, even in future versions? I am affected from this too and before I start changing the position of all the clocking out notes I would like to know where to move them. > Users should be warned to fix clock out notes taken by > affected Org releases. Existing important data following the interim > convention need to be fixed, transposing each affected clock out note > with the clock line. If both conventions are mixed, then, to identify > which clock line corresponds to each clock out note, either the user > will need to remember the time period when they used an affected > release, or remember directly which clock out line corresponds to each > ambiguous note, or analise the version history of their Org files. So > the longer the user takes to address the problem, the greater the > chance of data loss. I think this issue is important. > > Could we provide an Elisp function to fix this semi-automatically? This would be great. Ciao, Gregor -- -... --- .-. . -.. ..--.. ...-.-