From: Cody Goodman <codygman.consulting@gmail.com>
To: emacs-orgmode@gnu.org
Subject: org-capture with :prepend t breaks :clock-resume functionality in 9.1.9
Date: Fri, 25 Oct 2019 12:35:44 -0500 [thread overview]
Message-ID: <CADq_+R2fTQyyY0UrKDR3nUfLj=NRxCBDoAtkJbu_JGPRrXXORw@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 1238 bytes --]
I found a bug and traced down relevant pieces of it, but haven't figured
out how to fix the behavior of org-capture where `:prepend t`
`:clock-resume` works with and clock data from `:clock-in t` is visible
with:
```
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "file.org" "File")
"* TODO %?"
:clock-in t
:clock-resume t)))
```
If you add prepend into the mix though:
```
(setq org-capture-templates
'(("t" "Todo" entry (file+headline "file.org" "File")
"* TODO %?"
:clock-in t
:clock-resume t
:prepend t)))
```
You can no longer see the clocking data. Not the worst thing... right?
Well, :clock-resume depends on the clock-data being before point-max of the
capture buffer.
Causing the part that resumes the previous clock to never fire in
org-capture-finalize:
```
(and org-capture-clock-was-started
org-clock-marker
(eq (marker-buffer org-clock-marker) (buffer-base-buffer))
(>= org-clock-marker (point-min))
(< org-clock-marker (point-max))) ;; clock marker when :prepend t is
past point-max
```
My versions are:
Org mode version 9.1.9 (release_9.1.9-65-g5e4542 @
/home/cody/.emacs.d/straight/build/org/)
GNU Emacs 27.0.50 (build 1, x86_64-pc-linux-gnu, GTK+ Version 3.24.10)
[-- Attachment #2: Type: text/html, Size: 1601 bytes --]
next reply other threads:[~2019-10-25 17:36 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-25 17:35 Cody Goodman [this message]
2019-10-26 0:01 ` org-capture with :prepend t breaks :clock-resume functionality in 9.1.9 Cody Goodman
2020-02-12 16:45 ` Bastien
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='CADq_+R2fTQyyY0UrKDR3nUfLj=NRxCBDoAtkJbu_JGPRrXXORw@mail.gmail.com' \
--to=codygman.consulting@gmail.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 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).