From: Kaushal Modi <kaushal.modi@gmail.com>
To: Vikas Rawal <vikasrawal@gmail.com>
Cc: William Denton <wtd@pobox.com>,
org-mode mailing list <emacs-orgmode@gnu.org>
Subject: Re: #+latex_header blocks, or, managing lots of LaTeX headers
Date: Tue, 12 Apr 2022 10:34:22 -0400 [thread overview]
Message-ID: <CAFyQvY1vXmwD5=3W50TXCZeTOAL+e3_8u1zG_sXoy0nNBsqtiw@mail.gmail.com> (raw)
In-Reply-To: <CALtzAB103mztcWPiS5qJFoms+Cp7EFU877-qtVvmD-_GEU9zLA@mail.gmail.com>
On Mon, Apr 11, 2022 at 10:53 PM Vikas Rawal <vikasrawal@gmail.com> wrote:
>
> For a major project like this, I would just put these in a separate file, and include it using #+INCLUDE:
Org has a special keyword for the purpose of including *just the setup
stuff*: #+setupfile
See (org) Export Settings.
#+include is useful when you want to include setup stuff mixed with Org content.
#+setupfile will include only the setup stuff. I think that would mean
only the Org keywords (lines beginning with #+) will be imported.
Additionally, #+setupfile keyword can accept either a file path or a
web URL.
So I have this at the top of many of my Org files:
#+setupfile: https://cdn.rawgit.com/kaushalmodi/.emacs.d/master/misc/org-setupfile.org
That file has my common setup stuff like LaTeX headers, Org macros, etc.
next prev parent reply other threads:[~2022-04-12 14:38 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-04-12 0:46 #+latex_header blocks, or, managing lots of LaTeX headers William Denton
2022-04-12 2:51 ` Vikas Rawal
2022-04-12 14:34 ` Kaushal Modi [this message]
2022-04-12 6:16 ` Tim Cross
2022-04-12 8:02 ` Timothy
2022-04-12 8:55 ` Juan Manuel Macías
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to='CAFyQvY1vXmwD5=3W50TXCZeTOAL+e3_8u1zG_sXoy0nNBsqtiw@mail.gmail.com' \
--to=kaushal.modi@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=vikasrawal@gmail.com \
--cc=wtd@pobox.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.