emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Gregor Zattler <telegraph@gmx.net>
To: emacs-orgmode <emacs-orgmode@gnu.org>
Subject: location of clocking out notes (was: Re: Release 9.0.5)
Date: Sun, 26 Feb 2017 13:03:49 +0100	[thread overview]
Message-ID: <20170226120349.kkqc7vq2smjlyvqb@len.workgroup> (raw)
In-Reply-To: <CAJR3QnedcimBfN_A4qcVu0TS0A=onPFzAMAVc8v6eGOj4T5KBQ@mail.gmail.com>

Hi Jorge, Bastien, org-mode developers,
* Jorge Morais Neto <jorge13515@gmail.com> [10. Feb. 2017]:
> On 10 February 2017 at 11:53, Bastien <bzg@gnu.org> 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
-- 
 -... --- .-. . -.. ..--.. ...-.-

  parent reply	other threads:[~2017-02-26 12:04 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-02-10 13:53 Release 9.0.5 Bastien
2017-02-10 19:50 ` Jorge Morais Neto
2017-02-10 20:05   ` Bastien Guerry
2017-02-26 12:03   ` Gregor Zattler [this message]
2017-02-26 13:21     ` location of clocking out notes Nicolas Goaziou
2017-02-10 20:25 ` Release 9.0.5 Fabrice Popineau
2017-02-10 21:37   ` Fabrice Popineau
2017-02-10 22:44     ` Fabrice Popineau
2017-02-11  0:47       ` Nicolas Goaziou
2017-02-11 15:37         ` Fabrice Popineau
2017-02-13 16:26           ` Nicolas Goaziou
2017-02-11  9:29     ` Colin Baxter
2017-02-10 22:12 ` Russell Adams
2017-02-12 22:29 ` Merge 9.0.5 to emacs master? (Was: Release 9.0.5) Kaushal Modi
2017-02-12 23:41   ` Kyle Meyer
2017-02-13  9:05     ` Merge 9.0.5 to emacs master? Bastien Guerry
2017-02-13 16:32       ` Kyle Meyer
2017-02-13 16:58         ` Rasmus
2017-02-13 18:04           ` Kyle Meyer
2017-04-18 13:02             ` Kaushal Modi

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

  List information: https://www.orgmode.org/

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=20170226120349.kkqc7vq2smjlyvqb@len.workgroup \
    --to=telegraph@gmx.net \
    --cc=emacs-orgmode@gnu.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
Code repositories for project(s) associated with this public inbox

	https://git.savannah.gnu.org/cgit/emacs/org-mode.git

This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).