From: Carsten Dominik <carsten.dominik@gmail.com>
To: Scot Becker <scot.becker@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Bug: Footnotes in combination with LaTeX fragments is broken in latest trunk
Date: Sun, 29 Nov 2009 01:23:10 +0100 [thread overview]
Message-ID: <04CB85C8-8652-456B-B172-501D80A835BD@gmail.com> (raw)
In-Reply-To: <e0e1fe620911281121t47feccccy9d898724f0edae8e@mail.gmail.com>
Hi Björn, Scot,
I just fixed a bug in this are, it the problem gone now?
- Carsten
On Nov 28, 2009, at 8:21 PM, Scot Becker wrote:
> I noticed this this week as well. I don't know how to do a backtrace
> (though I'll look it up and try) but attached (and pasted below) is a
> sample file.
>
> Scot
> (Edit: and the backtrace)
>
> #+TITLE: Some Lorem
>
> * Heading
>
>
> If you do a \autocite{key_0000} followed by an org-footnote[fn:: You
> seem to get an error.] Does this happen for you too?
>
> The error is "Invalid use of `\' in replacement text."
>
> If you do a \autocite{key_0000} and break the line
> like this [fn:: No trouble now.] everything's fine. I notice this
> because I use long-lines mode.
>
> And I just realized that I do this kind of thing with some
> frequency:[fn:: See the fine discussion of this and other relevant
> matters in \fullcite{bibtexkey_0000}] Do I have any hope that that
> might be made to work? At the moment, it throws the same error. If I
> need to I can use LaTeX footnote for this kind of thing, since I
> already do live with the limitations that imposes (no HTML export).
>
>
> ----------------------
> Backtrace:
>
> Debugger entered--Lisp error: (error "Invalid use of `\\' in
> replacement text")
> replace-match("\\[1]")
> org-footnote-normalize(nil t)
> org-export-preprocess-string(#("#+TITLE: Some Lorem\n\n* Heading
> \n\n\nIf you do a \\autocite{key_0000} followed by an
> org-footnote[fn:: You seem to get an error.] Blah here.\n\nThe error
> is \"Invalid use of `\\' in replacement text.\"\n\nIf you do a
> \\autocite{key_0000} and break the line \nlike this [fn:: No trouble
> now.] everything's fine. I notice this because I use long-lines
> mode.\n\nAnd I just realized that I do this kind of thing with some
> frequency:[fn:: See the fine discussion of this and other relevant
> matters in \\fullcite{bibtexkey_0000}] Do I have any hope that that
> might be made to work? At the moment, it throws the same error. If I
> need to I can use LaTeX footnote for this kind of thing, since I
> already do live with the limitations that imposes (no HTML
> export).\n\n\n\n\n\n" 0 19 (fontified nil font-lock-fontified t
> :org-license-to-kill t) 19 20 (fontified nil :org-license-to-kill t)
> 20 21 (fontified nil) 21 23 (fontified nil) 23 31 (fontified nil) 31
> 34 (fontified nil) 34 138 (fontified nil) 138 347 (fontified nil) 347
> 746 (fontified nil) 746 751 (fontified nil)) :emph-multiline t
> :for-LaTeX t :comments nil :tags not-in-toc :priority nil :footnotes t
> :drawers nil :timestamps t :todo-keywords t :add-text nil
> :skip-before-1st-heading nil :select-tags ("export") :exclude-tags
> ("noexport") :LaTeX-fragments nil)
> org-export-as-latex(nil nil nil "*Org LaTeX Export*")
> org-export-as-latex-to-buffer(nil)
> call-interactively(org-export-as-latex-to-buffer)
> org-export(nil)
> call-interactively(org-export nil nil)
> <newbug.org>
- Carsten
next prev parent reply other threads:[~2009-11-29 0:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-11-28 12:57 Bug: Footnotes in combination with LaTeX fragments is broken in latest trunk Bjørn Arild Mæland
2009-11-28 17:54 ` Carsten Dominik
2009-11-28 19:21 ` Scot Becker
2009-11-29 0:23 ` Carsten Dominik [this message]
2009-12-01 0:06 ` Scot Becker
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=04CB85C8-8652-456B-B172-501D80A835BD@gmail.com \
--to=carsten.dominik@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=scot.becker@gmail.com \
/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).