Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Hi Achim, Achim Gratz strom...@nexgo.de writes: Your remark reminded me that I should look at the generic exporter in contrib. It needs an eval-while-compile wrapped (require 'cl) to compile and run cleanly. It also doesn't appear to recognize tables (or those are still copies from the ASCII export?). It looks like it works line-by-line, which seems a somewhat questionable choice, but then it was written for Org6.25… I suggest you look at EXPERIMENTAL/org-export.el. It parses an Org buffer and store it as a structured list. It's not yet completely syntax aware, but it is a move in the right direction. I'm willing to work on this now and will move forward. -- Bastien
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Hi Jambunathan, Jambunathan K kjambunat...@gmail.com writes: I also invite you to take a look at org-lparse and org-xhtml and org-odt that are built on top of it. As far as I'm aware org-lparse also works line by line. I don't think this is the right direction for a generic exporter, but maybe I overlooked some machinery in the files you mention. If that's the case, please point me to relevant part of the code! Thanks, -- Bastien
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Bastien b...@altern.org writes: I suggest you look at EXPERIMENTAL/org-export.el. I see. It parses an Org buffer and store it as a structured list. It's not yet completely syntax aware, but it is a move in the right direction. That looks like a much cleaner approach, but it is as you say, quite in its infancy. It looks like you expect the export backends to deal with the resulting structure by themselves. I could see an alternative approach using callbacks into the export backend or making the structure itself executable and have the export backend provide the function definitions. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Samples for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldSamplesExtra
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Nicolas Goaziou n.goaz...@gmail.com writes: _Note to self_ : I really wish we can come up with an exporter that exactly matches Org syntax. An element recognized/ignored in Org should be identically recognized/ignored during the export process without resorting to any trick (à la `org-protected' text property). Your remark reminded me that I should look at the generic exporter in contrib. It needs an eval-while-compile wrapped (require 'cl) to compile and run cleanly. It also doesn't appear to recognize tables (or those are still copies from the ASCII export?). It looks like it works line-by-line, which seems a somewhat questionable choice, but then it was written for Org6.25… I think it boils down to the question of having a formal org syntax. If that existed, all exporters (and much of the org core, I guess) could work on the parse tree (some list structure with lists as elements and the actual text as their leaf nodes) of the org document. Regards, Achim. -- +[Q+ Matrix-12 WAVE#46+305 Neuron microQkb Andromeda XTk Blofeld]+ Wavetables for the Waldorf Blofeld: http://Synth.Stromeko.net/Downloads.html#BlofeldUserWavetables
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Your remark reminded me that I should look at the generic exporter in contrib. It needs an eval-while-compile wrapped (require 'cl) to compile and run cleanly. It also doesn't appear to recognize tables (or those are still copies from the ASCII export?). It looks like it works line-by-line, which seems a somewhat questionable choice, but then it was written for Org6.25… I think it boils down to the question of having a formal org syntax. If that existed, all exporters (and much of the org core, I guess) could work on the parse tree (some list structure with lists as elements and the actual text as their leaf nodes) of the org document. I also invite you to take a look at org-lparse and org-xhtml and org-odt that are built on top of it. With some very minimal hackery it is possible to export a document to lisp-format. You seem to be behind tables for quite some time. One of the most significant re-write is in the callbacks for tables. When it comes to export, most of the magic happens in the pre-processing stage and not in the export backends itself. Regards, Achim. --
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Günter Kolousek k...@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 Are you saying that this worked in some earlier version and is not working in 7.7 and tip? Or that you only tried it in 7.7 and tip, found that it is not working and reported it as a bug? If the former, which version was it working in? If the latter, it might very well be the case that org-mode just does not support this: whether that's a bug or a feature is in the eye of the beholder. Personally, I'd be surprised if this ever worked.[fn:1] Whether it can be made to work is another matter - but then it is not a bug report, it is a feature request. It makes a difference because it would require different methods of attacking the problem: in the first case, I'd bisect the commits to find out who broke it; in the second case, I would know it's new functionality and would just try to implement it without breaking anything else and I wouldn't go hunting for a culprit.[fn:2] Nick Footnotes: [fn:1] ... but I could be wrong. [fn:2] Note that the I in this paragraph is purely rhetorical.
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Hello, Günter Kolousek k...@htlwrn.ac.at writes: Hi, using footnotes i.e. [2] inside #+begin_src #+end_src causes errors during export using orgmode 7.7 and tip. This should be fixed now. Thank you for reporting this. _Note to self_ : I really wish we can come up with an exporter that exactly matches Org syntax. An element recognized/ignored in Org should be identically recognized/ignored during the export process without resorting to any trick (à la `org-protected' text property). Regards, -- Nicolas Goaziou
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Nick Dokos nicholas.do...@hp.com writes:
Jambunathan K kjambunat...@gmail.com wrote:
Nick Dokos nicholas.do...@hp.com writes:
Günter Kolousek k...@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.
Re: [O] Bug: export failed when using footnotes inside src blocks [7.7]
Thanks a lot! Regards, Günter Am 2011-07-30 12:45, schrieb Nicolas Goaziou: Hello, Günter Kolousekk...@htlwrn.ac.at writes: Hi, using footnotes i.e. [2] inside #+begin_src #+end_src causes errors during export using orgmode 7.7 and tip. This should be fixed now. Thank you for reporting this. _Note to self_ : I really wish we can come up with an exporter that exactly matches Org syntax. An element recognized/ignored in Org should be identically recognized/ignored during the export process without resorting to any trick (à la `org-protected' text property). Regards,
