From: Nick Dokos <nicholas.dokos@hp.com>
To: Eric Schulte <schulte.eric@gmail.com>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: BUG: example/src blocks and latex export
Date: Fri, 19 Aug 2011 15:59:40 -0400 [thread overview]
Message-ID: <11869.1313783980@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Eric Schulte <schulte.eric@gmail.com> of "Fri, 19 Aug 2011 07:49:13 MDT." <8739gxo39e.fsf@gmail.com>
Eric Schulte <schulte.eric@gmail.com> wrote:
> > 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.
>
I tried evaluating the code block in the following file both with (my
probably slightly stale version of) master: Org-mode version 7.7
(release_7.7.120.g2edd) and the version with the patch applied: Org-mode
version 7.7 (release_7.7.121.gb267a)
--8<---------------cut here---------------start------------->8---
#+BABEL: :exports code
* foo
Verbiage to begin the paragraph
#+begin_src sh
date
#+end_src
and verbiage to end the same paragraph.
* bar
Verbiage to begin the paragraph
#+begin_example
date
#+end_example
and verbiage to end the same paragraph.
--8<---------------cut here---------------end--------------->8---
After C-c C-c in the code block, it looks like this in both cases:
--8<---------------cut here---------------start------------->8---
#+BABEL: :exports code
* foo
Verbiage to begin the paragraph
#+begin_src sh
date
#+end_src
#+results:
: Fri Aug 19 15:36:04 EDT 2011
and verbiage to end the same paragraph.
* bar
Verbiage to begin the paragraph
#+begin_example
date
#+end_example
and verbiage to end the same paragraph.
--8<---------------cut here---------------end--------------->8---
So I don't think the patch changes anything in the visual appearance of
the results. Am I missing something? Were you worried about this or
something else? Of course, the line after the results does become a new
paragraph in this case when exported to latex: there's yet *another*
newline inserted after the results, but that is a separate problem, and
the patch under discussion does not change that behavior at all.
Agreed?
Thanks,
Nick
next prev parent reply other threads:[~2011-08-19 19:59 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-08-19 10:09 BUG: example/src blocks and latex export Nick Dokos
2011-08-19 13:49 ` Eric Schulte
2011-08-19 15:27 ` Nick Dokos
2011-08-19 19:59 ` Nick Dokos [this message]
2011-08-19 21:27 ` Bastien
2011-08-19 22:03 ` Nick Dokos
2011-08-19 23:11 ` Nick Dokos
2011-08-21 18:30 ` Eric Schulte
2011-08-21 18:28 ` Eric Schulte
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=11869.1313783980@alphaville.dokosmarshall.org \
--to=nicholas.dokos@hp.com \
--cc=emacs-orgmode@gnu.org \
--cc=schulte.eric@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).