From: Nicolas Goaziou <n.goaziou@gmail.com>
To: CS Fuu <csfuu1@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: Cannot insert a footnote after certain verbatim text?
Date: Sun, 16 Oct 2011 10:15:04 +0200 [thread overview]
Message-ID: <87r52dl5dj.fsf@gmail.com> (raw)
In-Reply-To: <CAJAuE2VH0-tcUFBLxbgsWVpVkQXSOGb-ad6QT8bRhLU8GnEAGw@mail.gmail.com> (CS Fuu's message of "Fri, 14 Oct 2011 14:48:54 -0400")
Hello,
CS Fuu <csfuu1@gmail.com> writes:
> I am using org to write a document correcting some of my students' more
> common LaTeX blunders, and I keep running into places where I am not able to
> insert a footnote ("Cannot insert a footnote here."). Some of these problems
> I am unable to reproduce consistently, but I think it usually occurs when a
> paragraph (or list item) contains verbatim or code text with a backslash
> (\), and only after the verbatim text. Here is one such example. Create an
> .org file with the following three "paragraphs" (including the two blank
> likes):
>
>
> Blah, blah, blah.
>
> Woof, woof, =\begin{document}=, woof.
>
> Cry, cry, cry.
>
>
> If you're me, then you can insert a footnote after any word or punctuation
> in the first and third paragraphs, and after the first two words and the
> first comma in the second paragraph, but nowhere past the second comma in
> the second paragraph.
>
> I'm running the latest org (7.7) from the git repository in GNU emacs
> 23.1.1.
For what it's worth, this not directly related to footnotes. It's
a weakness in `org-inside-LaTeX-fragment-p', which returns a non-nil
value after =\begin{document}= instead of nil. And, obviously, one
cannot add a footnote inside a LaTeX fragment...
Regards,
--
Nicolas Goaziou
prev parent reply other threads:[~2011-10-16 8:16 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-10-14 18:48 Cannot insert a footnote after certain verbatim text? CS Fuu
2011-10-16 8:15 ` Nicolas Goaziou [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:
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=87r52dl5dj.fsf@gmail.com \
--to=n.goaziou@gmail.com \
--cc=csfuu1@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).