emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed

From: Nick Dokos <nicholas.dokos@hp.com>
To: Bastien <bzg@altern.org>
Cc: nicholas.dokos@hp.com, emacs-orgmode@gnu.org
Subject: Re: BUG: example/src blocks and latex export
Date: Fri, 19 Aug 2011 18:03:44 -0400	[thread overview]
Message-ID: <12981.1313791424@alphaville.dokosmarshall.org> (raw)
In-Reply-To: Message from Bastien <bzg@altern.org> of "Fri, 19 Aug 2011 23:27:47 +0200." <874o1d6qi4.fsf@gnu.org>

Bastien <bzg@altern.org> wrote:

> Hi Nick,
> 
> Nick Dokos <nicholas.dokos@hp.com> writes:
> 
> > * foo
> >
> > Verbiage to begin the paragraph
> > #+begin_src shell
> > get-config.py var section [section ...]
> > #+end_src
> > and verbiage to end the same paragraph.
> >
> > * bar
> >
> > Verbiage to begin the paragraph
> > #+begin_example
> > get-config.py var section [section ...]
> > #+end_example
> > and verbiage to end the same paragraph.
> 
> I tested your patch with the example above and I get this:
> 
> ,----
> | Verbiage to begin the paragraph
> | 
> | \lstset{language=shell}
> | \begin{lstlisting}
> | get-config.py var section [section ...]
> | \end{lstlisting}
> | 
> | and verbiage to end the same paragraph.
> | \section*{bar}
> | \label{sec-2}
> | 
> | 
> | Verbiage to begin the paragraph
> | 
> | \begin{verbatim}
> | get-config.py var section [section ...]
> | \end{verbatim}
> | and verbiage to end the same paragraph.
> `----
> 
> It looks better than the current export (less white lines) but still
> has a problem with the first "and verbiage..." being indented.
> 
> Is this intentional?  Or do you want the same behavior for #+begin_src
> and #+begin_example?
> 

Not intentional. But I have org-export-latex-listings set to nil, so in
my case, the src block gets turned into a verbatim environment, not into
a listings environment, and there is no empty line there.  Let me play
around a bit with org-export-latex-listings and see.

I guess the change in org-latex-verbatim-wrap takes care of my case,
but there is another (gratuitous?) newline inserted after listings.

> In overall, I think number of white lines should be the same in the
> Org source file and in the LaTeX exported file, so a patch here is
> welcome.  But maybe I misunderstood something in Eric's reply.

I tend to agree, but I can also understand Eric's wish for visual
separation.  However, as I pointed out in my earlier reply to him, I
think that's a separate problem, not addressed (or affected) by this
patch.

Thanks for testing,
Nick

next prev parent reply	other threads:[~2011-08-19 22:03 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
2011-08-19 21:27 ` Bastien
2011-08-19 22:03   ` Nick Dokos [this message]
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=12981.1313791424@alphaville.dokosmarshall.org \
    --to=nicholas.dokos@hp.com \
    --cc=bzg@altern.org \
    --cc=emacs-orgmode@gnu.org \
    /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

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).