From mboxrd@z Thu Jan 1 00:00:00 1970 From: Nick Dokos Subject: Re: BUG: example/src blocks and latex export Date: Fri, 19 Aug 2011 11:27:24 -0400 Message-ID: <9507.1313767644@alphaville.dokosmarshall.org> References: <6977.1313748571@alphaville.dokosmarshall.org> <8739gxo39e.fsf@gmail.com> Reply-To: nicholas.dokos@hp.com Return-path: Received: from eggs.gnu.org ([140.186.70.92]:40713) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QuQyp-0002sp-Jx for emacs-orgmode@gnu.org; Fri, 19 Aug 2011 11:27:32 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1QuQyl-0003tK-6y for emacs-orgmode@gnu.org; Fri, 19 Aug 2011 11:27:31 -0400 Received: from g4t0016.houston.hp.com ([15.201.24.19]:18579) by eggs.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1QuQyk-0003tG-VX for emacs-orgmode@gnu.org; Fri, 19 Aug 2011 11:27:27 -0400 In-Reply-To: Message from Eric Schulte of "Fri, 19 Aug 2011 07:49:13 MDT." <8739gxo39e.fsf@gmail.com> List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org To: Eric Schulte Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org Eric Schulte 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