From: Ihor Radchenko <yantar92@posteo.net>
To: Tommy Kelly <tommy.kelly@verilab.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [BUG] Invalid capture datetree capture templates (newly introduced) [9.7-pre (release_9.6.18-1145-g10d286 @ /home/jds6696/.emacs.d/straight/build/org/)]
Date: Fri, 09 Feb 2024 20:43:26 +0000 [thread overview]
Message-ID: <87a5o99xn5.fsf@localhost> (raw)
In-Reply-To: <CAMg28OttDprJ0-NGtSfkXiAqky8xSH=8JrjT_ngPHtacuU1X7w@mail.gmail.com>
Tommy Kelly <tommy.kelly@verilab.com> writes:
> C) entry (file+olp+datetree "test-datetree.org" "H1 "H2") ;;
> filename plus heading and sub-heading
>
> Then I'd expect A) to use a datetree rooted at the file top level; B)
> to use one underneath heading "* H1"; and C) to use one underneath **
> H2" (which itself is underneath "* H1").
> And in each case I'd expect it to create a new datetree at the
> specified location if one didn't already exist.
>
> HOWEVER, it looks like that can break if there is already one or more
> datetrees anywhere in the file AT A LEVEL BELOW THAT specified by the
> template.
> In that case, the position specified by the template is simply
> ignored. Instead, the captured item is filed at first occurring
> datetree of the above kind.
> To be clear, that's even if there is also a pre-existing datetree at
> the correct, template-specified location but further down the file.
Are you sure that what you describe is newly introduced?
I'd expect this exact behavior since forever, judging from how
`org-datetree--find-create' is implemented.
--
Ihor Radchenko // yantar92,
Org mode contributor,
Learn more about Org mode at <https://orgmode.org/>.
Support Org development at <https://liberapay.com/org-mode>,
or support my work at <https://liberapay.com/yantar92>
next prev parent reply other threads:[~2024-02-09 20:41 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-07 14:23 [BUG] Invalid capture datetree capture templates (newly introduced) [9.7-pre (release_9.6.18-1145-g10d286 @ /home/jds6696/.emacs.d/straight/build/org/)] Justin Silverman
2024-02-07 14:49 ` Ihor Radchenko
2024-02-09 19:13 ` Tommy Kelly
2024-02-09 20:43 ` Ihor Radchenko [this message]
2024-02-10 19:29 ` Tommy Kelly
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=87a5o99xn5.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=tommy.kelly@verilab.com \
/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).