emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: No Wayman <iarchivedmywholelife@gmail.com>
To: emacs-orgmode@gnu.org
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: Wed, 30 Dec 2020 21:23:51 -0500	[thread overview]
Message-ID: <87eej6bsvu.fsf@gmail.com> (raw)

Consider the following file named "/tmp/capture-item-logbook.org":

---- start capture-item-logbook.org ---
SCHEDULED: <2020-12-30 Wed 21:30 ++1d>
:STYLE:    habit
- State "DONE"       from "TODO"       [2020-12-29 Tue 21:30]

:+begin_src emacs-lisp :lexical t
(let ((org-capture-templates
       '(("x" "TASK ITEM" item
          (file+headline "/tmp/capture-item-logbook.org" 
  (org-capture nil "x"))
---- end capture-item-logbook.org ---

Executing the src block places the capture item in the LOGBOOK 
drawer if the entry type is 'item or 'checkitem.
Technically this is the correct behavior according to 
`org-capture-templates' docstring:

item  a plain list item, will be placed in the
    first plain list at the target location.
    Its default template is:
      "- %?"

The documentation on LOGBOOK drawers also mentions:

"You can also arrange for state change notes  and clock times to 
be stored in a ‘LOGBOOK’ drawer.
If you want to store a quick note there, in a similar way to state 
changes, use..." 

Is it worth having an option for org-capture's item/checkitem 
templates to skip targeting drawers?
capture is flexible enough where user's can implement their own 
point-placing function, but I wonder
if skipping drawers is the common case.


             reply	other threads:[~2020-12-31  2:41 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-31  2:23 No Wayman [this message]
  -- strict thread matches above, loose matches on Subject: below --
2020-12-31  6:31 [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/)] Sam Whitlock

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:

  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=87eej6bsvu.fsf@gmail.com \
    --to=iarchivedmywholelife@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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).