From: Bernt Hansen <bernt@norang.ca>
To: emacs-orgmode@gnu.org
Subject: BUG: Clocking in starts clock on the wrong task; Org-mode version 6.31trans (release_6.31.9.ga90f2)
Date: Thu, 1 Oct 2009 16:43:58 -0400 [thread overview]
Message-ID: <200910012043.n91KhwaG022049@gollum.intra.norang.ca> (raw)
If you narrow to subtree when there is a following task the narrowed
buffer has a blank line at the end. If you are on this line and
clock-in it starts the clock for the _following_ task (outside the
narrowed subtree) and not the task you are looking at.
I stumbled across this today because the following task was already
over the estimated limit when I clocked it in - which triggered my
alarm sound.
,----[ test.org ]
| #+STARTUP:
| * TODO One
| * TODO Two
`----
,----[ minimal.emacs ]
| (add-to-list 'load-path (expand-file-name "~/git/org-mode/lisp"))
| (add-to-list 'auto-mode-alist '("\\.\\(org\\|org_archive\\|txt\\)$" . org-mode))
| (require 'org-install)
|
| (global-set-key "\C-cl" 'org-store-link)
| (global-set-key "\C-ca" 'org-agenda)
| (global-set-key "\C-cb" 'org-iswitchb)
`----
Key sequence to reproduce:
$ emacs -q -l minimal.emacs test.org
| Key | Notes |
|-------------------------------+-------------------------------|
| C-n | Go to first task '* TODO One' |
| M-x org-narrow-to-subtree RET | Narrow to subtree |
| C-n | Move to last blank line |
| C-c C-x C-i | Clock in (next) task |
|-------------------------------+-------------------------------|
-Bernt
Emacs : GNU Emacs 22.2.1 (i486-pc-linux-gnu, GTK+ Version 2.12.11)
of 2008-11-09 on raven, modified by Debian
Package: Org-mode version 6.31trans (release_6.31.8.g7485)
next reply other threads:[~2009-10-01 20:44 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 20:43 Bernt Hansen [this message]
2009-10-02 6:42 ` BUG: Clocking in starts clock on the wrong task; Org-mode version 6.31trans (release_6.31.9.ga90f2) Carsten Dominik
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=200910012043.n91KhwaG022049@gollum.intra.norang.ca \
--to=bernt@norang.ca \
--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).