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: Wed, 18 Jan 2017 22:39:36 +0100 [thread overview]
Message-ID: <87inpcyrmv.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <3e1b98b7-3ff9-130c-a4ee-e36b63b88c3b@juno.com> (Francis J. Monari's message of "Wed, 18 Jan 2017 11:53:11 -0500")
Hello,
"Francis J. Monari, Esquire" <monarifj.esq@juno.com> writes:
> Using Clock Mode to track time.
> Org Mode starts and stops clock. Clock entry redirected to CLOCK
> drawer.
> I expect to see the clock entry (time & note) appear in CLOCK drawer.
> What happens is that clock time goes to CLOCK drawer, clock note goes to
> LOGBOOK drawer.
> This allocation does not make sense. Time is properly tracked, but no
> ability to identify activity.
> org mode clock variables follow:
> ;;;Org clock settings
> (add-hook 'org-clock-in-prepare-hook 'org-resolve-clocks)
> (setq org-clock-history-length 32)
> (setq org-clock-idle-time 20)
> (setq org-clock-in-resume t)
> (setq org-clock-into-drawer "CLOCK")
Why do you specify a different drawer name if you want notes and clocks
in the same one?
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2017-01-18 21:39 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 [this message]
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
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=87inpcyrmv.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).