From: Russell Adams <RLAdams@AdamsInfoServ.Com> To: email@example.com Subject: Re: RFC: Consistent Latex (& html) publishing environment Date: Thu, 18 Nov 2010 22:10:46 -0600 [thread overview] Message-ID: <20101119041046.GD3139@x201> (raw) In-Reply-To: <firstname.lastname@example.org> On Thu, Nov 18, 2010 at 10:51:49PM -0500, Nick Dokos wrote: > [This doesn't seem to have made it out to the list for some reason, > so trying again.] > > Russell Adams <RLAdams@AdamsInfoServ.Com> wrote: > > > ... > > This is great, but pops up an emacs session. If I run emacs in --batch > > mode, it won't load my init file and so loses some of my export > > customizations... > > > > You can load your init file explicitly: > > emacs --batch --load <init-file> ... Certainly! And yet, should I be depending on my init file while trying to provide a consistent environment across documents? That's the crux of the matter. Put everything into init files and use it for everything when it seems to need customization, or make a document completely selfcontained and somehow sync settings across docs? That's why I was asking how other folks accomplish similar tasks. Thanks. ------------------------------------------------------------------ Russell Adams RLAdams@AdamsInfoServ.com PGP Key ID: 0x1160DCB3 http://www.adamsinfoserv.com/ Fingerprint: 1723 D8CA 4280 1EC9 557F 66E8 1154 E018 1160 DCB3
next prev parent reply other threads:[~2010-11-19 4:11 UTC|newest] Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top 2010-11-18 22:50 Russell Adams 2010-11-19 3:51 ` Nick Dokos 2010-11-19 4:10 ` Russell Adams [this message] 2010-11-19 19:45 ` Mark Elston
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=20101119041046.GD3139@x201 \ --email@example.com \ --firstname.lastname@example.org \ --subject='Re: RFC: Consistent Latex (& html) publishing environment' \ /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
Code repositories for project(s) associated with this 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).