Eric Schulte <schulte.e...@gmail.com> wrote: > If you want results embedded into a paragraph, then I would suggest > using an inline code block. Regular code blocks are "blocks" in that > they will break paragraphs and are treated (in my mind) more like > figures than inline elements. >
Actually in my "real" case, I was using ``:exports code'' in a #+BABEL header, but I forgot to include that in the test. > > > > I get sane behavior with the attached patch, but I'm wondering if it > > breaks other backends, so if somebody is willing to test, I'd appreciate > > it (and of course, I'll test as well). For the time being at least, this > > is a trial balloon, not a real patch. > > > > Thanks for the patch, I would not want this behavior on by default > because I think the results in the Org-mode file are less visually > pleasing than when results are padded with spaces. Perhaps this > behavior could be controlled through a new header argument which would > default to the current behavior. > OK - I did not test evaluation at all: thanks for reminding me. > > ISTR this issue coming up on the list recently: did I imagine it? > > A similar issue regarding the insertion of spaces through repeated > evaluation and removal of results of a code block has been discussed > recently. I'm pushing up a small fix for that issue now. > I'll keep an eye out for it. Thanks, Nick
