emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Peter Davis <pfd@pfdstudio.com>
To: emacs-orgmode@gnu.org
Subject: Re: Forcing line breaks in src (monospace) examples
Date: Tue, 23 Jun 2015 11:30:26 -0400	[thread overview]
Message-ID: <55897B92.7020907@pfdstudio.com> (raw)
In-Reply-To: <CAFyQvY2O3TVqBMFNaZW9Rw9AF6u6ud8Efh1oByteroz+JRyQ0A@mail.gmail.com>

[-- Attachment #1: Type: text/plain, Size: 836 bytes --]

Thanks!

I think for my purposes with HTML, it would be sufficient to replace 
<pre>...</pre> with <tt>...</tt>. Is there a way to get org to do that 
on export, or do I have to keep editing the HTML output?

Thank you.

-pd


On 6/23/15 11:11 AM, Kaushal wrote:
> On the topic of exporting auto-wrapped lines in source code blocks to 
> .tex/.pdf:
>
> If you use minted instead of listings, the latest minted 2.0 (probably 
> not yet on tex-live) latex package does line wrapping in the source 
> code blocks very elegantly.
...
>
>
> On Tue, Jun 23, 2015 at 10:59 AM Peter Davis <pfd@pfdstudio.com 
> <mailto:pfd@pfdstudio.com>> wrote:
>
>
>     So getting line breaks in exported LaTeX/PDF src examples is now
>     working
>     beautifully.
>
>     Is there any way to do this in exported HTML?
>
>     Thank you,
>     -pd
>
>
>


[-- Attachment #2: Type: text/html, Size: 1997 bytes --]

      reply	other threads:[~2015-06-23 15:30 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-06-14 14:44 Forcing line breaks in src (monospace) examples Peter Davis
2015-06-14 14:51 ` Peter Davis
2015-06-14 15:36   ` Robert Klein
2015-06-14 15:53     ` Peter Davis
2015-06-14 16:11       ` Robert Klein
2015-06-14 16:23         ` Peter Davis
2015-06-14 16:36           ` Peter Davis
2015-06-14 16:38           ` Robert Klein
2015-06-14 17:01             ` Peter Davis
2015-06-23 14:59               ` Peter Davis
2015-06-23 15:11                 ` Kaushal
2015-06-23 15:30                   ` Peter Davis [this message]

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=55897B92.7020907@pfdstudio.com \
    --to=pfd@pfdstudio.com \
    --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
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).