From: "Eric Schulte" <schulte.eric@gmail.com>
To: Nicolas Goaziou <n.goaziou@gmail.com>
Cc: emacs-orgmode@gnu.org
Subject: Re: [PATCH] comments exporting
Date: Tue, 15 Jun 2010 08:48:43 -0700 [thread overview]
Message-ID: <87aaqwi9es.fsf@gmail.com> (raw)
In-Reply-To: <87hbl4tpmi.wl%n.goaziou@gmail.com> (Nicolas Goaziou's message of "Tue, 15 Jun 2010 15:03:01 +0200")
Hi Nicolas,
Thanks for the thoughtful response.
Nicolas Goaziou <n.goaziou@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
next prev parent reply other threads:[~2010-06-15 16:01 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-13 23:25 [PATCH] lists and exportation to latex Nicolas Goaziou
2010-06-14 7:40 ` Nicolas Goaziou
2010-06-14 17:32 ` Eric Schulte
2010-06-14 18:10 ` Eric Schulte
2010-06-14 20:07 ` [PATCH] comments exporting Nicolas Goaziou
2010-06-14 21:36 ` Eric Schulte
2010-06-15 13:03 ` Nicolas Goaziou
2010-06-15 15:48 ` Eric Schulte [this message]
2010-06-15 16:32 ` Nicolas Goaziou
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=87aaqwi9es.fsf@gmail.com \
--to=schulte.eric@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=n.goaziou@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).