emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: bug in org-element-footnote-definition-parser?
Date: Thu, 09 Jan 2014 08:41:36 -0500	[thread overview]
Message-ID: <87fvox5l2n.fsf@gmail.com> (raw)
In-Reply-To: loom.20140109T052552-182@post.gmane.org

Mark Edgington <edgimar@gmail.com> writes:

> Nick Dokos <ndokos <at> gmail.com> writes:
>> Nicolas Goaziou <n.goaziou <at> gmail.com> writes:
>> > Hello,
>> >
>> > Mark Edgington <edgimar <at> gmail.com> writes:
>> >
>> >> I have encountered the following error message when trying to export
>> >> to latex the attached example org file:
>> >>
>> >> org-element-footnote-definition-parser: Invalid search bound (wrong
>> >> side of point)
>> >>
>> I 'm not sure but I believe this was a bug in emacs that Eli Zaretskii
>> fixed recently.  You will need to update your emacs. In the git mirror I
>> use, the commit appears like this:
>> commit b2b5f414358a7835b56613f67d2b0278ee804290
>> Author: Eli Zaretskii <eliz <at> gnu.org>
>> Date:   Wed Jan 1 19:44:48 2014 +0200
> Hi Nick,
> I can confirm that updating emacs to 24.3.1 does eliminate the problem. 
> But, what this means is that the problem will exist for any users who are
> still using Emacs 23 -- and maybe this shouldn't concern anyone since
> normally using bleeding-edge org-mode code would coincide with using newer
> versions of emacs...

No, I don't think so: this was a bug in a caching mechanism that was
introduced (disabled) in emacs 24 - it was enabled a couple of months
ago. It should not affect any emacs 23 users.


      reply	other threads:[~2014-01-09 13:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-01-08 16:59 bug in org-element-footnote-definition-parser? Mark Edgington
2014-01-08 17:37 ` Nicolas Goaziou
2014-01-08 18:21   ` Nick Dokos
2014-01-09  4:30     ` Mark Edgington
2014-01-09 13:41       ` Nick Dokos [this message]

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:

  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=87fvox5l2n.fsf@gmail.com \
    --to=ndokos@gmail.com \
    --cc=emacs-orgmode@gnu.org \


* 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


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).