From: Bastien <bzg@altern.org>
To: nicholas.dokos@hp.com
Cc: emacs-orgmode@gnu.org
Subject: Re: BUG: example/src blocks and latex export
Date: Fri, 19 Aug 2011 23:27:47 +0200 [thread overview]
Message-ID: <874o1d6qi4.fsf@gnu.org> (raw)
In-Reply-To: <6977.1313748571@alphaville.dokosmarshall.org> (Nick Dokos's message of "Fri, 19 Aug 2011 06:09:31 -0400")
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?
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.
Thanks,
--
Bastien
next prev parent reply other threads:[~2011-08-19 21:27 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 [this message]
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=874o1d6qi4.fsf@gnu.org \
--to=bzg@altern.org \
--cc=emacs-orgmode@gnu.org \
--cc=nicholas.dokos@hp.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).