From: Eric Abrahamsen <eric@ericabrahamsen.net>
To: emacs-orgmode@gnu.org
Subject: Re: a more inteligant way of signaling the exporter to start a new line than "\\"?
Date: Mon, 19 Oct 2015 23:23:07 -0400 [thread overview]
Message-ID: <87eggqkyuc.fsf@ericabrahamsen.net> (raw)
In-Reply-To: CAOQHXPob1ijbxdqz=SjyMxn5yPxd8jB4SYm7JLRk3yEir9yeNA@mail.gmail.com
Xebar Saram <zeltakc@gmail.com> writes:
> Thanks so much Eric
>
> that helped me alot :)
>
> appreciate it
And, if the time ever comes that you really do want to preserve line
breaks for some reason, you can set the org-export-preserve-breaks
variable to t, or use the \n:nil OPTIONS line.
>
> Z
>
> On Mon, Oct 19, 2015 at 4:34 PM, Eric S Fraga <e.fraga@ucl.ac.uk>
> wrote:
>
>
> On Monday, 19 Oct 2015 at 16:10, Xebar Saram wrote:
> > Hi
> >
> > This maybe a really stupid neewb question, but when im writing
> my slides
> > and course homework in org and export to reveal html, pdf etc i
> always get
> > all lines stitched together and the only way i managed to get
> over this is
> > use a "\\" sign at the end of EACH line. this is really
> cumbersome. I
> > wonder how you more experienced guys deal with this? am i
> missing
> > something? cant the exporter just use emacs lines as lines? why
> are they
> > getting joined during export?
>
> Essentially you want each line to be a separate "paragraph" so
> simply
> leave a blank line in between:
>
> #+begin_src org
> ,*** Basic data types in R
> Decimals values like 4.5 are called numerics
>
> Natural numbers like 4 are called integers. Integers are also
> numerics
> #+end_src
>
> --
> : Eric S Fraga (0xFFFCF67D), Emacs 24.5.1, Org
> release_8.3beta-1229-ge900eb
prev parent reply other threads:[~2015-10-20 3:23 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-19 13:10 a more inteligant way of signaling the exporter to start a new line than "\\"? Xebar Saram
2015-10-19 13:34 ` Eric S Fraga
2015-10-19 14:05 ` Xebar Saram
2015-10-19 14:25 ` Eric S Fraga
2015-10-20 3:23 ` Eric Abrahamsen [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=87eggqkyuc.fsf@ericabrahamsen.net \
--to=eric@ericabrahamsen.net \
--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).