From: Bill Powell <bill@billpowellisalive.com>
To: nicholas.dokos@hp.com
Cc: Eraldo Helal <eraldo@eraldo.org>, Org-Mode <emacs-orgmode@gnu.org>
Subject: Re: keep newlines on pdf export
Date: Mon, 14 Dec 2009 10:18:53 -0500 [thread overview]
Message-ID: <874ontmvmq.wl%bill@billpowellisalive.com> (raw)
In-Reply-To: <32418.1260747778@gamaville.dokosmarshall.org>
At Sun, 13 Dec 2009 18:42:58 -0500,
Nick Dokos wrote:
>
> Eraldo Helal <eraldo@eraldo.org> wrote:
>
> > One other reason behind this is that I can not export my document to
> > html anymore after I added "\\" at the end of every line... well I can
> > but it does not look the way I want it to be. =]
> >
>
> The \obeylines method should not affect the HTML export.
>
> Nick
Hi folks,
I also have been using the \obeylines technique. But it seems a bit
crufty. I do lots of work in LaTeX, so I have a sense of the perils
involved in LaTeX linebreaking. Unfortunately, I have zero experience
with elisp, so I can't tackle this (yet).
The problem with the \obeylines hack is that if it's not properly
closed with a final bracket, your file breaks. But how do you keep
this final bracket in place? You can't move headlines around with the
usual reckless abandon, because there's no way (that I know of) to
keep that final bracket locked at the end of your text file. Unless
you want to enter an \obeylines within every headline ...
So I would give a +1 to \n:t giving at least rudimentary linebreak
support for PDF export, rather than silently failing. As someone who
regularly has to export the same file to both HTML and PDF, I would
rather have an option that works 90% of the time and sometimes
requires an arcane LaTeX fix (and is documented as such), than
/always/ have to use an arcane LaTeX fix.
Thanks,
Bill Powell
next prev parent reply other threads:[~2009-12-14 15:15 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <eraldo@eraldo.org>
2009-12-13 1:04 ` keep newlines on pdf export Eraldo Helal
2009-12-13 18:21 ` Nick Dokos
2009-12-13 20:51 ` Eraldo Helal
2009-12-13 20:53 ` Eraldo Helal
2009-12-13 23:42 ` Nick Dokos
2009-12-14 15:18 ` Bill Powell [this message]
2009-12-14 14:58 ` andrea
2009-12-14 15:35 ` Carsten Dominik
2009-12-14 21:56 ` Bill Powell
2009-12-14 22:20 ` Nick Dokos
2009-12-14 23:25 ` Bill Powell
2009-12-16 4:05 ` Eraldo Helal
2009-12-16 6:24 ` Carsten Dominik
2009-12-14 3:40 ` Nick Dokos
2009-12-14 7:49 ` Carsten Dominik
2009-12-13 2:39 Eraldo Helal
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=874ontmvmq.wl%bill@billpowellisalive.com \
--to=bill@billpowellisalive.com \
--cc=emacs-orgmode@gnu.org \
--cc=eraldo@eraldo.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).