From: Nick Dokos <ndokos@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: bug in org-element-footnote-definition-parser?
Date: Wed, 08 Jan 2014 13:21:44 -0500 [thread overview]
Message-ID: <87ppo2fi6f.fsf@alphaville.bos.redhat.com> (raw)
In-Reply-To: 8761pubci4.fsf@gmail.com
Nicolas Goaziou <n.goaziou@gmail.com> writes:
> Hello,
>
> Mark Edgington <edgimar@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@gnu.org>
Date: Wed Jan 1 19:44:48 2014 +0200
Fix bug #16265 with buffer caches when modifying text in indirect buffers.
src/search.c (newline_cache_on_off, find_newline): In indirect
buffers, use the newline cache of the base buffer.
src/insdel.c (invalidate_buffer_caches): If BUF is an indirect
buffer, invalidate the caches of its base buffer.
src/indent.c (width_run_cache_on_off, compute_motion): In indirect
buffers, use the width-run cache of the base buffer.
src/xdisp.c (redisplay_window): When the window displays an indirect
buffer, and the character widths in the display table have
changed, invalidate the width-run cache of the corresponding base
buffer.
src/fileio.c (Finsert_file_contents): When invalidating the newline
cache, consider the case of inserting into indirect buffer.
src/bidi.c (bidi_paragraph_cache_on_off, bidi_find_paragraph_start):
In indirect buffers, use the paragraph cache of the base buffer.
Nick
next prev parent reply other threads:[~2014-01-08 18:22 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 [this message]
2014-01-09 4:30 ` Mark Edgington
2014-01-09 13:41 ` Nick Dokos
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=87ppo2fi6f.fsf@alphaville.bos.redhat.com \
--to=ndokos@gmail.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).