From: Aaron Ecay <aaronecay@gmail.com>
To: Eric S Fraga <e.fraga@ucl.ac.uk>,
Emacs Org mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: error in capture
Date: Mon, 18 Jul 2016 14:31:31 +0100 [thread overview]
Message-ID: <87h9bn2hu4.fsf@gmail.com> (raw)
In-Reply-To: <87poqb1egz.fsf@ucl.ac.uk>
Hi Eric,
It’s a known bug in recent versions of org and/or emacs. No one knows
exactly what triggers the problem yet, and it’s being discussed in the
emacs bug tracker <https://debbugs.gnu.org/cgi/bugreport.cgi?bug=23917>.
--
Aaron Ecay
next prev parent reply other threads:[~2016-07-18 13:31 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-18 9:29 error in capture Eric S Fraga
2016-07-18 13:31 ` Aaron Ecay [this message]
[not found] ` <e020870037634b9b99b730fc98668680@HE1PR01MB1898.eurprd01.prod.exchangelabs.com>
2016-07-18 13:43 ` Eric S Fraga
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=87h9bn2hu4.fsf@gmail.com \
--to=aaronecay@gmail.com \
--cc=e.fraga@ucl.ac.uk \
--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).