From: Ethan Blanton <elb@psg.com>
To: emacs-orgmode@gnu.org
Subject: org-clock-find-position confusion (bug?)
Date: Sat, 27 Sep 2008 23:49:23 -0400 [thread overview]
Message-ID: <20080928034922.GA22412@elb.elitists.net> (raw)
[-- Attachment #1.1: Type: text/plain, Size: 1265 bytes --]
Thanks for taking care of my last issue so quickly; as a reward, I've
found another one! ;-) (Seriously, thanks for the blazing turn
around last time -- and thanks for org-mode, I'm finding a lot of
things to love!)
org-clock-find-position (6.07b again) displays unexpected behavior
when it encounters a clock line preceding a bulleted list.
Specifically, when a :CLOCK: drawer is created, the drawer encompasses
the first list item. E.g.:
* Heading
CLOCK: [2008-09-27 Sat 14:00]--[2008-09-27 Sat 14:30] => 0:30
- Bullet 1
- Bullet 2
Clocking in on this item again will yield (if drawer creation is
enabled):
* Heading
:CLOCK:
CLOCK: [2008-09-27 Sat 15:00]
CLOCK: [2008-09-27 Sat 14:00]--[2008-09-27 Sat 14:30] => 0:30
- Bullet 1
:END:
- Bullet 2
Looking at org-clock-find-position, this seems to be intentional;
removing the (if (org-at-item-p) (org-end-of-item)) statement "fixes"
this behavior for me, but may be breaking something else which I am
not seeing.
Ethan
--
The laws that forbid the carrying of arms are laws [that have no remedy
for evils]. They disarm only those who are neither inclined nor
determined to commit crimes.
-- Cesare Beccaria, "On Crimes and Punishments", 1764
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 189 bytes --]
[-- Attachment #2: Type: text/plain, Size: 204 bytes --]
_______________________________________________
Emacs-orgmode mailing list
Remember: use `Reply All' to send replies to the list.
Emacs-orgmode@gnu.org
http://lists.gnu.org/mailman/listinfo/emacs-orgmode
next reply other threads:[~2008-09-28 3:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-28 3:49 Ethan Blanton [this message]
2008-09-28 5:16 ` org-clock-find-position confusion (bug?) Carsten Dominik
2008-09-28 13:22 ` Ethan Blanton
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20080928034922.GA22412@elb.elitists.net \
--to=elb@psg.com \
--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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.