From: Tommy Kelly <tommy.kelly@verilab.com>
To: 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: Sat, 10 Feb 2024 13:29:35 -0600 [thread overview]
Message-ID: <CAMg28OsxfL1Rv-S9zDOMubvj3Yn6aPMdY9AAif_rd8u2h=oX0Q@mail.gmail.com> (raw)
In-Reply-To: <87a5o99xn5.fsf@localhost>
In response to Tommy Kelly <tommy.kelly@verilab.com> writing:
>> ...if there is already one or more datetrees anywhere in [a] file AT A LEVEL
>> BELOW THAT specified by [a datetree-based capture] template [then] the
>> position specified by the template is simply ignored.
Ihor Radchenko <yantar92@posteo.net> wrote:
> 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.
No, I'm not sure. In fact, now you mention it, what you're suggesting
probably is the case. This is the first time I've tried using more
than one datetree in the same file, so I wouldn't before have noticed
the behavior I describe.
That said, had I noticed it in the past, I would have been inclined to
flag it as an issue. At very least it makes the documentation
incorrect, but in fact I'd say that the documentation is fine and the
behavior is wrong.
Nevertheless, it's not connected with the issue you already fixed
(https://list.orgmode.org/878r3xfm90.fsf@localhost/T/#t) so that
should remain closed.
thx.
prev parent reply other threads:[~2024-02-10 19:31 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
2024-02-10 19:29 ` Tommy Kelly [this message]
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='CAMg28OsxfL1Rv-S9zDOMubvj3Yn6aPMdY9AAif_rd8u2h=oX0Q@mail.gmail.com' \
--to=tommy.kelly@verilab.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).