From: Xebar Saram <zeltakc@gmail.com>
To: org mode <emacs-orgmode@gnu.org>
Subject: Re: trying to write a guidebook for students using org , need help with formating
Date: Tue, 22 Oct 2013 14:14:52 +0200 [thread overview]
Message-ID: <CAOQHXPoJvb5zpOuCUurBXC=8McEJedKc13ugKqvwOp2uUzXQzw@mail.gmail.com> (raw)
In-Reply-To: <20131022093943.GX6656@kuru.dyndns-at-home.com>
[-- Attachment #1: Type: text/plain, Size: 1692 bytes --]
Thank you all
"I think `org-export-preserve-breaks' is the option you want. Try setting
it in a single buffer with #+OPTIONS:\n:nil and see what happens..."
that sounds interesting, but i couldn't understand how to use it (again im
still an org novice:) )
do i stick this line at the start:
#+OPTIONS:\n:nil
is that ^^ syntax correct?
best
Z
On Tue, Oct 22, 2013 at 12:39 PM, Suvayu Ali <fatkasuvayu+linux@gmail.com>wrote:
> On Tue, Oct 22, 2013 at 09:55:12AM +0200, Xebar Saram wrote:
> >
> > I'm trying to write a simple guidebook for my students in a GIS course.
> > Everything works great apart for the life of me i cant get the hang of
> > formatting and specifically how to insert (automatically?) line breaks so
> > that its discrete lines and not a paragraph. i think one can use '\\' to
> > indicate a line break but since its a guidebook "form" there are almost
> no
> > paragraphs and most line are 1 liners, so it seems to me crazy to go over
> > hundred lines of text and attach a \\ at the end. What am i missing here?
> >
> > i hope i made sense :) any help or documentation links would be really
> > appreciated!
> >
> > I'm attaching a short example of my org file, note that where i want
> single
> > lines i add a empty space between lines but still in the exporter it
> > creates a paragraph out of these lines
> >
>
> I think you are better off trying to do this with a specialised LaTeX
> class. A quick search led me to this TeX.SX question:
> <http://tex.stackexchange.com/q/3852>. You could also try using lists,
> just disable the bullets with an option in an #+attr_latex line.
>
>
> GL,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
>
[-- Attachment #2: Type: text/html, Size: 3623 bytes --]
next prev parent reply other threads:[~2013-10-22 12:14 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-22 7:55 trying to write a guidebook for students using org , need help with formating Xebar Saram
2013-10-22 8:16 ` Glyn Millington
2013-10-22 8:25 ` Eric Abrahamsen
2013-10-22 9:39 ` Suvayu Ali
2013-10-22 12:14 ` Xebar Saram [this message]
2013-10-23 1:00 ` Eric Abrahamsen
2013-10-23 6:11 ` Xebar Saram
2013-10-23 8:56 ` Eric Abrahamsen
2013-10-23 12:23 ` Xebar Saram
2013-10-23 13:41 ` Eric Abrahamsen
2013-10-23 14:23 ` Glyn Millington
2013-10-23 18:19 ` Xebar Saram
2013-10-23 22:15 ` Glyn Millington
2013-10-24 5:37 ` Eric Abrahamsen
2013-10-24 10:43 ` Suvayu Ali
2013-10-24 14:53 ` Xebar Saram
2013-10-27 6:49 ` Xebar Saram
2013-10-23 13:32 ` Rick Frankel
2013-10-22 16:42 ` Rick Frankel
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='CAOQHXPoJvb5zpOuCUurBXC=8McEJedKc13ugKqvwOp2uUzXQzw@mail.gmail.com' \
--to=zeltakc@gmail.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).