From: Ihor Radchenko <yantar92@posteo.net>
To: Justin Silverman <jsilve24@gmail.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: Wed, 07 Feb 2024 14:49:16 +0000 [thread overview]
Message-ID: <87h6ik49eb.fsf@localhost> (raw)
In-Reply-To: <87zfwccpvs.fsf@gmail.com>
Justin Silverman <jsilve24@gmail.com> writes:
> I have been using the same capture templates for years now without problem. Recently updated org and noticed a new bug.
>
> Example: the following capture template now produces an error:
> let: Invalid capture target specification: (file+olp+datetree "~/Dropbox/org/mtx-michelle.org")
>
> ("mp" "meeting psu" entry (file+olp+datetree "~/Dropbox/org/meetings_psu.org")
> "* MEETING %u with %? :MEETING:\n "
> :jump-to-captured t
> :tree-type month)
> Org no longer allows the third argument in (file+olp+datetree "~/Dropbox/org/meetings_psu.org") to be omitted. Everything works if I embed the datetree under a headline "foo" and make the capture template
Duplicate of https://list.orgmode.org/878r3xfm90.fsf@localhost/T/#t
Canceled.
--
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-07 14:46 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 [this message]
2024-02-09 19:13 ` Tommy Kelly
2024-02-09 20:43 ` Ihor Radchenko
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=87h6ik49eb.fsf@localhost \
--to=yantar92@posteo.net \
--cc=emacs-orgmode@gnu.org \
--cc=jsilve24@gmail.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).