From: "Colin Baxter 😺" <email@example.com>
To: Michael Eliachevitch <firstname.lastname@example.org>
Cc: , email@example.com
Subject: Re: [BUG] Plain capture template clocks into following headline instead of given olp [9.5.1 (release_9.5.1-15-gdb4805 @ /usr/share/emacs/29.0.50/lisp/org/)]
Date: Tue, 07 Dec 2021 12:43:59 +0000 [thread overview]
Message-ID: <firstname.lastname@example.org> (raw)
In-Reply-To: <email@example.com> (Michael Eliachevitch's message of "Tue, 07 Dec 2021 11:12:04 +0000")
[-- Attachment #1: Type: text/plain, Size: 1173 bytes --]
>>>>> Michael Eliachevitch <firstname.lastname@example.org> writes:
> Hello, I found a potential bug in org which I can reproduce with a
> minimal configuration.
> I added some org-capture templates purely for clocking into tasks
> via the capture-menu. These capture templates are for things I
> want to time-track but don't want to create a special entry for
> (like eating and breaks), so I used the `plain' type with an empty
> `""' template hoping it would clock into the given olp:
> (setq org-capture-templates '(( "c" "clock into") ("cu"
> "Unintended" plain (file+olp "~/org/clock_test.org" "Time sinks"
> "Unintended") "" :clock-in t :clock-keep t :immediate-finish t)
> ("ce" "Eating" plain (file+olp "~/org/clock_test.org" "Time sinks"
> "Eating") "" :clock-in t :clock-keep t :immediate-finish t)))
> My `clock_test.org' has the following headings:
> * Time sinks ** Unintended ** Eating
This is amazing. I have run into exactly the same problem. I was
wondering whether to report it!
Oh, and I can reproduce the bug with your ECM.
Thanks for reporting it.
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 511 bytes --]
next prev parent reply other threads:[~2021-12-07 12:46 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-07 11:12 Michael Eliachevitch
2021-12-07 12:43 ` Colin Baxter 😺 [this message]
2021-12-07 18:54 ` Michael Eliachevitch
2021-12-08 7:28 ` Colin Baxter 😺
2021-12-08 7:48 ` Ihor Radchenko
2021-12-08 8:17 ` Colin Baxter 😺
2021-12-19 13:08 ` Ihor Radchenko
2022-05-15 6:18 ` Ihor Radchenko
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:
List information: https://www.orgmode.org/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
* 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
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).