From: "Martin Schöön" <martin.schoon@gmail.com>
To: "emacs-orgmode@gnu.org" <emacs-orgmode@gnu.org>
Subject: Re: Using KOMA and Memoir?
Date: Fri, 9 May 2014 20:59:23 +0200 [thread overview]
Message-ID: <CAHxk2pCQGwEY4KPEwF+baYCMSKbca7ZEJOV74vLEiYVP_KK_UA@mail.gmail.com> (raw)
In-Reply-To: <20140509105837.GA2634@chitra.no-ip.org>
[-- Attachment #1: Type: text/plain, Size: 1776 bytes --]
On 9 May 2014 12:58, Suvayu Ali <fatkasuvayu+linux@gmail.com> wrote:
> On Fri, May 09, 2014 at 09:46:15AM +0100, Eric S Fraga wrote:
> > On Thursday, 8 May 2014 at 22:17, Martin Schöön wrote:
> >
> > which is what several of us have been trying to get across! At the very
> > least, you need:
> >
> > ,----
> > | (add-to-list 'load-path ...org lisp directory...)
> > | (require 'org)
> > | (require 'ox-latex)
> > | (add-to-list 'org-latex-classes ...)
> > `----
> >
> > to do what you want! You are missing the third line.
> >
> > A minimal initialisation with just those four lines should be enough to
> > see if org with KOMA works.
>
> For your understanding, you can do a simple test. Start emacs without
> the add-to-list line. Then evaluate these:
>
> (featurep 'org)
> (featurep 'ox-latex)
>
> You will get t for the first, nil for the second.
>
> Now try to find the variable org-latex-classes with C-h v. You will not
> be able to find it. Now load ox-latex with either load-library or by
> evaluating (require 'ox-latex). Try the above evaluations again, you
> will see t for both, and when you try to find the variable with C-h v,
> you will succeed.
>
> AFAIU, the exporter loads enabled backends when you do the first export.
> So when you modify a variable that is defined in an unloaded module, of
> course this does not work! Hope this makes the problem and the
> resolution clearer.
>
> To get some hints about doing things right, I would point you to my
> setup: <https://github.com/suvayu/.emacs.d/blob/master/org-mode-config.el>
>
> Hope this helps,
>
> --
> Suvayu
>
> Open source is the future. It sets us free.
>
--
Martin Schöön
http://hem.bredband.net/b262106/index.html
[-- Attachment #2: Type: text/html, Size: 2580 bytes --]
next prev parent reply other threads:[~2014-05-09 18:59 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-05-05 17:36 Using KOMA and Memoir? Martin Schöön
2014-05-05 18:31 ` Eric S Fraga
2014-05-05 20:23 ` Martin Schöön
2014-05-06 7:34 ` Eric S Fraga
2014-05-06 19:41 ` Martin Schöön
2014-05-06 21:28 ` Suvayu Ali
2014-05-07 5:48 ` Martin Schöön
2014-05-07 8:26 ` Ian Barton
2014-05-07 19:42 ` Martin Schöön
2014-05-07 7:38 ` Eric S Fraga
2014-05-07 20:09 ` Martin Schöön
2014-05-07 20:44 ` Nick Dokos
2014-05-07 21:03 ` Martin Schöön
2014-05-07 21:19 ` Martin Schöön
2014-05-07 22:29 ` Suvayu Ali
2014-05-08 6:08 ` Martin Schöön
2014-05-08 12:58 ` Suvayu Ali
2014-05-08 20:17 ` Martin Schöön
2014-05-09 8:46 ` Eric S Fraga
2014-05-09 10:58 ` Suvayu Ali
2014-05-09 18:59 ` Martin Schöön [this message]
2014-05-09 19:33 ` Martin Schöön
2014-05-09 19:55 ` Eric S Fraga
2014-05-08 7:39 ` Eric S Fraga
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=CAHxk2pCQGwEY4KPEwF+baYCMSKbca7ZEJOV74vLEiYVP_KK_UA@mail.gmail.com \
--to=martin.schoon@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).