On Sat, 3 Nov 2018 at 08:34, Nicolas Goaziou <m...@nicolasgoaziou.fr> wrote: > > Philip Hudson <phil.hud...@iname.com> writes: > > > Why? This is a regression. > > You have something in your configuration that no longer works.
Agreed. > Generally > speaking, that could be a plain regression, indeed. But you may also > have been relying on unspecified behavior: this might be a documentation > bug. Also agreed. > 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. > 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. Have you tested that case and confirmed that my report is correct? > You seem to capture something that doesn't correspond to this > definition, hence the error. That is a completely erroneous leap of logic. Try the minimal failing case. > Note that keywords are global, so you could > equivalently write: > > * Baz > #+FOO: bar Agreed, understood. > Maybe the documentation could be clearer, too. Suggestions welcome. The doco seems fine to me. I relied on it for the definition of my template, which has worked as expected for years. -- Phil Hudson http://hudson-it.ddns.net Pretty Good Privacy (PGP) ID: 0x4E482F85
