From: Suvayu Ali <fatkasuvayu+linux@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: trying to write a guidebook for students using org , need help with formating
Date: Thu, 24 Oct 2013 12:43:57 +0200 [thread overview]
Message-ID: <20131024104357.GK1769@kuru.dyndns-at-home.com> (raw)
In-Reply-To: <8761sndyas.fsf@ericabrahamsen.net>
Hello Xebar,
On Thu, Oct 24, 2013 at 01:37:31PM +0800, Eric Abrahamsen wrote:
> Xebar Saram <zeltakc@gmail.com> writes:
>
> > Thanks again guys
> >
> > Rick: "But a better approach would be to define your own latex list
> > environment for
> > program steps and use lists:"
> >
> > ive never used latex, do you mind expanding on that a bit?
> >
> > Eric: "I don't think it's cut, is it? I just tried with your example
> > and long
> > lines are preserved as-is (ie, quite long)"
> > this is how it looks in my pdf export:
> >
> > https://paste.xinu.at/sYsMVz/
>
> Oh I see -- it's latex that cuts those lines off, not the org exporter.
> You'll probably want to go the list route then. See this link for how to
> create a custom list environment:
>
> http://www.troubleshooters.com/linux/lyx/ownlists.htm
>
> Then do this in org, replacing "bogus" with the name of your new environment:
>
> #+ATTR_LATEX: :environment bogus
> - this is a
> - list with some
> - items in it
I guess you missed my response. I suggested this a couple of days back.
Sadly I was in a hurry and could not provide precise instructions. You
can achieve this using the enumitem package with the noitemsep option[1].
So inside Org all you need to do is add the following to the file header:
#+LATEX_HEADER: \usepackage{enumitem}
If you want this behaviour for all lists add the following:
#+LATEX_HEADER: \setlist{nolistsep}
If you only want to do this for a particular kind of list (say,
enumerate) add the following line instead:
\setenumerate{noitemsep}
To control this per-list you can do:
#+attr_latex: :options noitemsep
- Step 1
- Step 2
- Step 3
For more info on other options, see the documentation for enumitem
(`texdoc enumitem' or <http://ctan.org/pkg/enumitem>).
Hope this helps,
Footnotes:
[1] See this TeX.SX question for more details:
<http://TeX.stackexchange.com/q/10684>.
--
Suvayu
Open source is the future. It sets us free.
next prev parent reply other threads:[~2013-10-24 10:44 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
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 [this message]
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=20131024104357.GK1769@kuru.dyndns-at-home.com \
--to=fatkasuvayu+linux@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).