Hi Nicolas, Thanks for the thoughtful response.
Nicolas Goaziou <n.goaz...@gmail.com> writes: > Hello, >>>>>> Eric Schulte writes: > >> Not to look a gift patch in the mouth, but while this patch fixes the >> above issue it looks like it introduces a new problem. > > If you want a quick hack, just remove the space I introduced in the > comment regexp. But, imho, it isn't a real solution as #+source is > definitely not a comment and should not be caught by the regexp > comments. > yes, I suppose so. When our #+source and #+results statements always started on column zero they were being cleaned up later in the export cycle so this wasn't a problem. > > I don't know yet what org-babel is really doing with the #+source > and #+results lines, but if they are no longer needed for exportation, > there should be a function to clean them before exporting. > Agreed, I'll take a look at this org-babel pre-processing later today and add in functionality to clean up #+source: and #+results: lines. > > In addition, there is another problem. In the example below, the > second item actually starts a brand new list upon exporting. > This problem I can't reproduce. > > ** comments not commented > # $some stuff > # some more stuff$ -- I should be a comment line > > 1) a source block inside of an =enumerate= > #+source: plotxy > #+begin_src emacs-lisp :exports results > (message "I think so") > #+end_src > > can cause problems > > 2) another line > after Org-babel pre-processing the above is converted to the following for me --8<---------------cut here---------------start------------->8--- # $some stuff # some more stuff$ -- I should be a comment line 1) a source block inside of an =enumerate= #+source: plotxy #+results: plotxy : I think so can cause problems 2) another line --8<---------------cut here---------------end--------------->8--- which exports to latex as expected. Hopefully after I've made the above changes this list interruption will cease, if not then I'll need to find an example I can reproduce. > > > If I had to take a guess, I'd say that org-babel messes with > indentation and org-latex, being very sensitive about indentation when > it comes to lists, gets disoriented. > > So, is the result replacing the source code in the same > column as the #+begin_src ? > yup, it's the same column, the only possible culprit I can see is two empty lines (notice those are not indented but are truly empty) between the #+source and #+results lines. > > So I think something has to be fixed in org-babel. > > I will look at it tomorrow, > > Regards, Thanks, as always, for your help -- Eric _______________________________________________ Emacs-orgmode mailing list Please use `Reply All' to send replies to the list. Emacs-orgmode@gnu.org http://lists.gnu.org/mailman/listinfo/emacs-orgmode
