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/)]

In response to Tommy Kelly 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 wrote: > Are you sure that what

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/)]

Tommy Kelly 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

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/)]

Justin Silverman writes: js > Org no longer allows the third argument in (file+olp+datetree ... And Ihor Radchenko replied: ir > Duplicate of https://list.orgmode.org/878r3xfm90.fsf@localhost/T/#t ir > Canceled. The initial problem has certainly been fixed in that the headline(s) arguments to

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/)]

Justin Silverman 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 >

[BUG] Invalid capture datetree capture templates (newly introduced) [9.7-pre (release_9.6.18-1145-g10d286 @ /home/jds6696/.emacs.d/straight/build/org/)]

Remember to cover the basics, that is, what you expected to happen and what in fact did happen. You don't know how to make a good report? See Your bug report will be posted to the Org mailing list.