From: Jambunathan K <kjambunathan@gmail.com>
To: nicholas.dokos@hp.com
Cc: ko@htlwrn.ac.at, emacs-orgmode@gnu.org
Subject: Re: Bug: export failed when using footnotes inside src blocks [7.7]
Date: Sat, 30 Jul 2011 16:23:59 +0530 [thread overview]
Message-ID: <81pqksuji0.fsf@gmail.com> (raw)
In-Reply-To: <8571.1312019903@alphaville.dokosmarshall.org> (Nick Dokos's message of "Sat, 30 Jul 2011 05:58:23 -0400")
Nick Dokos <nicholas.dokos@hp.com> writes:
> Jambunathan K <kjambunathan@gmail.com> wrote:
>
>> Nick Dokos <nicholas.dokos@hp.com> writes:
>>
>> > Günter Kolousek <ko@htlwrn.ac.at> wrote:
>> >
>> >>
>> >> Hi, using footnotes i.e. [2] inside #+begin_src #+end_src causes errors
>> >> during export using orgmode 7.7 and tip.
>> >>
>> >> Günter
>> >>
>> >> ...
>> >>
>> >> * Test
>> >> foo
>> >> #+begin_src python
>> >> lst = [-1, -2, 2, -3, -4]
>> >>
>> >> for x in lst[:]:
>> >> if x < 0:
>> >> lst.remove(x)
>> >>
>> >> print(lst) # [2] <- does not work!
>> >> #+end_src
>> >>
>>
>> This should set the thing to rest.
>>
>
> Acctually, no: I took the OP's request (and I presume I misled you into
> thinking that too) as a functionality request, but I didn't read it
> carefully enough. I think he is complaining about getting an error (see
> the attached backtrace).
Right, it shouldn't crash.
FWIW, The problem is (org-footnote-get-next-reference ...) sees the
following text while looking for next reference.
\begin{verbatim}
lst = [-1, -2, 2, -3, -4]
for x in lst[:]:
if x < 0:
lst.remove(x)
print(lst) # [2] <- does not work!
\end{verbatim}
AFAICS the above text has no text decorations as well.
Naturally org-footnote-get-next-reference is misled into believing that
it is in the "allowed" territory.
Jambunathan K.
>
> Nick
>
>
>
>> ,----[ C-h v org-footnote-forbidden-blocks RET ]
>> | org-footnote-forbidden-blocks is a variable defined in `org-footnote.el'.
>> | Its value is
>> | ("example" "verse" "src" "ascii" "beamer" "docbook" "html" "latex" "odt")
>> |
>> |
>> | Documentation:
>> | Names of blocks where footnotes are not allowed.
>> |
>> | [back]
>> `----
>>
>> OP can search for for alternative ways to reference code block lines in
>> the following section of the manual
>> http://orgmode.org/org.html#Literal-examples
>>
>> (Hint: Search for ref:jump)
>>
>>
>> Jambunathan K.
>>
next prev parent reply other threads:[~2011-07-30 10:54 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-07-30 8:22 Bug: export failed when using footnotes inside src blocks [7.7] Günter Kolousek
2011-07-30 9:00 ` Nick Dokos
2011-07-30 9:19 ` Jambunathan K
2011-07-30 9:58 ` Nick Dokos
2011-07-30 10:53 ` Jambunathan K [this message]
2011-07-30 10:45 ` Nicolas Goaziou
2011-07-30 14:34 ` Günter Kolousek
2011-07-31 18:41 ` Achim Gratz
2011-07-31 19:12 ` Jambunathan K
2011-08-14 16:29 ` Bastien
2011-08-14 16:25 ` Bastien
2011-08-14 16:54 ` Achim Gratz
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=81pqksuji0.fsf@gmail.com \
--to=kjambunathan@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=ko@htlwrn.ac.at \
--cc=nicholas.dokos@hp.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).