From: Philip Hudson <phil.hudson@iname.com>
To: 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: Fri, 2 Nov 2018 00:24:56 +0000 [thread overview]
Message-ID: <CAJ1MqVFATTH6EYCMkhqMQBXik1nZEr+v7wQrrBFHHM-4yMWHSg@mail.gmail.com> (raw)
In-Reply-To: <87ftwkbhxs.fsf@nicolasgoaziou.fr>
On Thu, 1 Nov 2018 at 22:12, Nicolas Goaziou <mail@nicolasgoaziou.fr> wrote:
>
> Philip Hudson <phil.hudson@iname.com> writes:
>
> Could you show your template? Could you explain how you initiate the
> capture process (e.g., with arguments)? Also, could you show the desired
> output?
Here's a minimal failing capture-completed template:
------- Cut here ------
#+FOO: bar
* Baz
------ Cut here ------
Pass this into `org-capture-verify-tree'. This will reproduce the error.
My fix strips out the leading in-buffer settings for the duration of
that call only. Effectively what gets passed into
`org-capture-verify-tree' is then this:
------- Cut here ------
* Baz
------- Cut here ------
--
Phil Hudson http://hudson-it.ddns.net
Pretty Good Privacy (PGP) ID: 0x4E482F85
next prev parent reply other threads:[~2018-11-02 0:25 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 [this message]
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
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=CAJ1MqVFATTH6EYCMkhqMQBXik1nZEr+v7wQrrBFHHM-4yMWHSg@mail.gmail.com \
--to=phil.hudson@iname.com \
--cc=emacs-orgmode@gnu.org \
/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).