From: Sam Whitlock <email@example.com>
To: firstname.lastname@example.org, email@example.com
Subject: [feature] capture: defcustom for item/checkitem to skip LOGBOOK [9.4.4 (release_9.4.4-159-g9140a7 @ /home/n/.emacs.d/straight/build/org/)]
Date: Thu, 31 Dec 2020 07:31:16 +0100 [thread overview]
Message-ID: <CAAS9WOtVCd3cXjOaM4Qe9TBmnr7ru4YRRa9vtKG=AYXfqYeCiQ@mail.gmail.com> (raw)
[-- Attachment #1: Type: text/plain, Size: 996 bytes --]
I just saw this discussion on /r/emacs and came here to share my thoughts.
I have worked around this behavior for a while and think having an option
to skip logging into the drawer would be useful.
My own workflow that this behavior (bug?) currently affects is as follows
(similar to the reddit thread):
- use org-habit to track a weekly TODO list heading
- use a capture template to log checkitem type entries into this heading
Due to this quirk, the capture template logs into the drawer instead
(matching the checkitem regex).
I would consider this to be a bug, as I'm not sure if anyone would use a
capture template to deliberately log into the LOGBOOK drawer.
Additionally, if the LOGBOOK is empty, it does log to the correct place
(i.e. the contents of the heading).
Because the location varies based on the LOGBOOK being empty or not, I
think it would be good to either have it always log into the LOGBOOK or not
when capturing (specifically, the behavior of `org-capture-place-item`).
[-- Attachment #2: Type: text/html, Size: 2279 bytes --]
next reply other threads:[~2020-12-31 6:32 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-31 6:31 Sam Whitlock [this message]
-- strict thread matches above, loose matches on Subject: below --
2020-12-31 2:23 [feature] capture: defcustom for item/checkitem to skip LOGBOOK [9.4.4 (release_9.4.4-159-g9140a7 @ /home/n/.emacs.d/straight/build/org/)] No Wayman
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).