From: Stefan Nobis <stefan-ml@snobis.de>
To: emacs-orgmode@gnu.org
Subject: Re: New Orgmode LaTex Document Class ?
Date: Fri, 28 Jul 2023 09:57:19 +0200 [thread overview]
Message-ID: <m1o7jw31uo.fsf@nobis-it.eu> (raw)
In-Reply-To: <SJ0PR03MB5455C5502B0CCE4B4C4DECB8A206A@SJ0PR03MB5455.namprd03.prod.outlook.com> (David Masterson's message of "Thu, 27 Jul 2023 23:47:09 -0700")
David Masterson <dsmasterson@gmail.com> writes:
> I want to install a resume document class for LaTex
There are the variables org-latex-classes and org-latex-default-class
on the Org side, but that's only about some structural metadata (how
to map Org headline levels to LaTeX structure macros).
To find the new class file you have to put it into a folder where
LaTeX will find it. Org just puts the name of the class into the TeX
file and everything else is up to LaTeX.
Usually, on Unix systems, there is the optional hierarchy $HOME/texmf
where you can store you private, local files. It is a good idea to
mimic the usual TeX directory structure, therefore class and style
files for LaTeX should go into $HOME/texmf/tex/latex (you may add
subdirectories there).
Nowadays it should suffice to just drop your class file there and
everything should work on the LaTeX side.
A quick check whether LaTeX will be able to find the file could be
done with the tool kpsewhich:
kpsewhich myltxclass.cls
This tool uses the same configuration and search algorithms for the
files as the TeX engines. So if kpsewhich finds the file, the engines
should find it too.
One side note: On macOS the default path for the user texmf tree is
$HOME/Library/texmf. On all systems you may find the correct base
directory for the user texmf tree with the command
kpsewhich -var-value TEXMFHOME
Hope this helps.
--
Until the next mail...,
Stefan.
next prev parent reply other threads:[~2023-07-28 8:18 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-07-28 6:47 New Orgmode LaTex Document Class ? David Masterson
2023-07-28 7:23 ` Ihor Radchenko
2023-07-28 7:57 ` Stefan Nobis [this message]
2023-07-29 22:58 ` David Masterson
2023-07-30 4:27 ` Ihor Radchenko
2023-07-30 5:02 ` David Masterson
2023-07-30 6:42 ` Ihor Radchenko
2023-07-30 20:34 ` David Masterson
2023-07-31 7:05 ` Ihor Radchenko
2023-07-31 7:40 ` Stefan Nobis
2023-07-31 10:23 ` Ihor Radchenko
2023-07-31 22:41 ` David Masterson
2023-08-01 8:11 ` Ihor Radchenko
2023-08-02 6:28 ` David Masterson
2023-08-02 6:52 ` Ihor Radchenko
2023-08-02 6:59 ` Ihor Radchenko
2023-08-02 17:14 ` David Masterson
2023-08-03 7:58 ` [PATCH] org-manual: Add references to LaTeX docs (was: New Orgmode LaTex Document Class ?) Ihor Radchenko
2023-08-06 3:35 ` [PATCH] org-manual: Add references to LaTeX docs David Masterson
2023-08-06 8:04 ` Ihor Radchenko
2023-08-02 7:49 ` New Orgmode LaTex Document Class ? tomas
2023-08-02 16:53 ` David Masterson
2023-08-02 17:29 ` tomas
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=m1o7jw31uo.fsf@nobis-it.eu \
--to=stefan-ml@snobis.de \
--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).