From: Nicolas Goaziou <mail@nicolasgoaziou.fr>
To: Philip Hudson <phil.hudson@iname.com>
Cc: emacs orgmode-mailinglist <emacs-orgmode@gnu.org>
Subject: Re: Bug: Capture template insertion fails with #+FOO [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/phil/.emacs.d/elpa/org-9.1.14/)]
Date: Sun, 04 Nov 2018 15:03:49 +0100 [thread overview]
Message-ID: <8736sh9by2.fsf@nicolasgoaziou.fr> (raw)
In-Reply-To: <CAJ1MqVG3mRyx6fBdUuywwzdWNh-nftFY0OXUNP8dNyOobRNc2g@mail.gmail.com> (Philip Hudson's message of "Sat, 3 Nov 2018 09:09:46 +0000")
Hello,
Philip Hudson <phil.hudson@iname.com> writes:
> On Sat, 3 Nov 2018 at 08:34, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>> I cannot see your template, since you did not send it yet. I assume it
>> uses an `entry' type.
>
> No assumption involved. I stated so plainly.
Indeed.
>> Barring `plain', all capture types enforce
>> a certain structure for contents. The `entry' type expects a node, which
>> is roughly a headline plus contents, as noted in the manual:
>>
>> ‘entry’
>> An Org mode node, with a headline. Will be filed as the child
>> of the target entry or as a top-level entry. The target file
>> should be an Org file.
>
> Agreed, understood, and 100% the case in both my case (I'm afraid
> you'll just have to take my word for it) and in the trivial but
> effectively illustrative minimal failing case I gave you.
No, it is not the case. AFAIU, in the minimal failing case, you capture
#+FOO: bar
* Baz
This is _not_ a node. A node starts with a headline and everything is
contained within that headline. So it doesn't qualify as a valid `entry'
capture type.
> The doco seems fine to me. I relied on it for the definition of my
> template, which has worked as expected for years.
It might be that you misinterpreted the definition of a node. Hence my
suggestion to improve the documentation.
In any case, you can simply move the keywords below the headline, and be
done with it.
Regards,
--
Nicolas Goaziou
next prev parent reply other threads:[~2018-11-04 14:04 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-29 22:47 Bug: Capture template insertion fails with #+FOO [9.1.14 (9.1.14-1-g4931fc-elpa @ /home/phil/.emacs.d/elpa/org-9.1.14/)] Philip Hudson
2018-11-01 10:04 ` Philip Hudson
2018-11-01 21:34 ` Nicolas Goaziou
2018-11-02 0:24 ` Philip Hudson
2018-11-02 1:35 ` Nicolas Goaziou
2018-11-02 9:22 ` Philip Hudson
2018-11-03 8:34 ` Nicolas Goaziou
2018-11-03 9:09 ` Philip Hudson
2018-11-04 14:03 ` Nicolas Goaziou [this message]
2018-11-04 16:31 ` Philip Hudson
2018-11-05 21:46 ` Nicolas Goaziou
2018-11-06 19:24 ` Philip Hudson
2018-11-10 10:39 ` Nicolas Goaziou
2018-11-10 15:06 ` Philip Hudson
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=8736sh9by2.fsf@nicolasgoaziou.fr \
--to=mail@nicolasgoaziou.fr \
--cc=emacs-orgmode@gnu.org \
--cc=phil.hudson@iname.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).