From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Jorge Morais Neto <jorge13515@gmail.com>
Cc: org mode <emacs-orgmode@gnu.org>
Subject: Re: Bug: Org separates clock out note from the clock line [9.0.4 (9.0.4-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20170124/)]
Date: Fri, 03 Feb 2017 22:57:45 +0100 [thread overview]
Message-ID: <87efzfrl7q.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJR3QnePvgj9RqD0Pask6dfhXiND0ugirpysccgHLtZUh+Tk1Q@mail.gmail.com> (Jorge Morais Neto's message of "Tue, 31 Jan 2017 16:52:59 -0200")
Hello,
Jorge Morais Neto <jorge13515@gmail.com> writes:
> Hi. I have started this instance of GNU Emacs 25.1.91.1 with an empty init
> file and then I customized org-log-note-clock-out to t. Then I created a
> new Org buffer with a single level 1 headline, and set property
> CLOCK_INTO_DRAWER to nil. I then clocked in and then out, adding a note.
> The note was stored outside any drawer (as requested) and above the clock
> line. Then I clocked in and out again, adding a second note. The result
> was:
>
> * Teste
> :PROPERTIES:
> :CLOCK_INTO_DRAWER: nil
> :END:
> - Teste 2.
> - Teste 1.
> CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:13] => 0:01
> CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:12] => 0:00
>
> "teste" is Portuguese for "test".
>
> I expected the "Teste 1" line to stay in its place above the corresponding
> clock line, like this:
>
> * Teste
> :PROPERTIES:
> :CLOCK_INTO_DRAWER: nil
> :END:
> - Teste 2.
> CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:13] => 0:01
> - Teste 1.
> CLOCK: [2017-01-31 Tue 14:12]--[2017-01-31 Tue 14:12] => 0:00
Fixed. Thank you.
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2017-02-03 21:57 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-31 18:52 Bug: Org separates clock out note from the clock line [9.0.4 (9.0.4-elpaplus @ /home/jorge/.emacs.d/elpa/org-plus-contrib-20170124/)] Jorge Morais Neto
2017-02-03 21:57 ` Nicolas Goaziou [this message]
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=87efzfrl7q.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=jorge13515@gmail.com \
/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).