From mboxrd@z Thu Jan 1 00:00:00 1970 From: Philip Hudson 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: Sat, 3 Nov 2018 09:09:46 +0000 Message-ID: References: <87ftwkbhxs.fsf@nicolasgoaziou.fr> <87ftwk9s8e.fsf@nicolasgoaziou.fr> <877ehua7ab.fsf@nicolasgoaziou.fr> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:44661) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gIrwj-0005bX-7V for emacs-orgmode@gnu.org; Sat, 03 Nov 2018 05:10:22 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gIrwf-0006fL-Vw for emacs-orgmode@gnu.org; Sat, 03 Nov 2018 05:10:21 -0400 Received: from mail-pf1-f179.google.com ([209.85.210.179]:45835) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gIrwW-0006Qa-NN for emacs-orgmode@gnu.org; Sat, 03 Nov 2018 05:10:10 -0400 Received: by mail-pf1-f179.google.com with SMTP id p17-v6so1731162pfj.12 for ; Sat, 03 Nov 2018 02:10:01 -0700 (PDT) In-Reply-To: <877ehua7ab.fsf@nicolasgoaziou.fr> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: emacs orgmode-mailinglist On Sat, 3 Nov 2018 at 08:34, Nicolas Goaziou wrote= : > > Philip Hudson 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: > > =E2=80=98entry=E2=80=99 > 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. --=20 Phil Hudson http://hudson-it.ddns.net Pretty Good Privacy (PGP) ID: 0x4E482F85