From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: "Francis J. Monari, Esquire" <monarifj.esq@juno.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: clock comments [9.0.2 (9.0.2-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-plus-contrib-20161214/)]
Date: Sat, 28 Jan 2017 00:13:56 +0100 [thread overview]
Message-ID: <878tpwt7t7.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <a05fb9b2-ba8f-c453-6fda-02a595a02a94@juno.com> (Francis J. Monari's message of "Tue, 24 Jan 2017 12:42:12 -0500")
Hello,
"Francis J. Monari, Esquire" <monarifj.esq@juno.com> writes:
> The question remains "How can I make the notes associated with the Clock
> entry follow the Clock entry?
Short answer : put everything in the same drawer, i.e., LOGBOOK.
Long answer :
I considered re-introducing the behaviour you suggest, but there is one
issue.
When `org-clock-into-drawer' is set to an integer, an the number of
clocks in the entry get past it, all pre-existing clocks are moved to
log drawer (by default "LOGBOOK"). Unfortunately, it is not possible to
preserve association between the note and the clock (i.e., the list item
after the clock may or may not be a note relative to the clock). So we
cannot guarantee that both the note and the clock are always kept
together.
Basically, the two features are incompatible.
I'm open to suggestions.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-01-27 23:14 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-01-18 16:53 Bug: clock comments [9.0.2 (9.0.2-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-plus-contrib-20161214/)] Francis J. Monari, Esquire
2017-01-18 21:39 ` Nicolas Goaziou
2017-01-18 22:00 ` Bug: clock comments [9.0.2 (9.0.2-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-plus-contrib-20161214/)] {response to question} Francis J. Monari, Esquire
2017-01-24 17:42 ` Bug: clock comments [9.0.2 (9.0.2-elpaplus @ c:/USR/FJM/APP/.emacs.d/elpa/org-plus-contrib-20161214/)] Francis J. Monari, Esquire
2017-01-27 23:13 ` Nicolas Goaziou [this message]
2017-02-03 21:57 ` Nicolas Goaziou
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=878tpwt7t7.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=monarifj.esq@juno.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).