emacs-orgmode@gnu.org archives
 help / color / mirror / code / Atom feed
From: Glyn Millington <glyn.millington@gmail.com>
To: emacs-orgmode@gnu.org
Subject: Re: latex markup in org?
Date: Sun, 01 Jun 2014 08:09:44 +0100	[thread overview]
Message-ID: <87bnudxg07.fsf@nowhere.org> (raw)
In-Reply-To: 87vbslkth3.fsf@stevenarntson.com

Steven Arntson <steven@stevenarntson.com> writes:

> I've been learning to export from org to latex (to pdf), and have had
> great success. There's a simplification to the process I'd like to make,
> though, if it's possible.
>
> Right now I use files: file.org and filestyle.sty. The .sty gives
> the latex-specific instruction, and I point to it from file.org with a
> line of #+LATEX_HEADER: \usepackage{filestyle}. This works great, but
> I'd love to have just one file, not two, to keep things simple.
>
> So I tried putting the contents of filestyle.sty near the top of file.org
> inside of #+BEGIN_latex and #+END_latex, but it doesn't quite work. It
> incompletely works, which is perplexing...
>
> I'd appreciate any ideas about this--can it be done?

I'm sure it can, but not that way!

As I understand it, blocks like this ....

#+BEGIN_LaTeX
\marginpar{\color{red} \tiny \raggedright
\vspace{18pt}
Lorem ipsum dolor sit amet, consectetuer adipiscing elit, sed diam
nonummy nibh euismod tincidunt ut laoreet dolore magna aliquam erat
volutpat.}
#+END_LaTeX

work where they are and not file-wide.

For file-wide instructions you need to put 'em in 

#+LATEX_HEADER lines.

Exactly how to do that will depend on the precise contents of
filestyle.sty.

atb



Glyn

  parent reply	other threads:[~2014-06-01  9:03 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-06-01  6:57 latex markup in org? Steven Arntson
2014-06-01  7:03 ` Omid
2014-06-01  7:09 ` Glyn Millington [this message]
2014-06-01 19:26 ` John Kitchin
2014-06-02  0:09   ` Steven Arntson

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=87bnudxg07.fsf@nowhere.org \
    --to=glyn.millington@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).