From mboxrd@z Thu Jan 1 00:00:00 1970 From: ckelty ckelty Subject: Re: letterhead and signature in odt export Date: Tue, 30 Oct 2018 20:50:03 -0700 Message-ID: <2FD78D67-FE7A-4114-BE48-0DCE7F435E35@gmail.com> References: <87r2g7rkkw.fsf@gmail.com> <877ehzpnrv.fsf@gmail.com> <6EFB79F4-F86A-4544-A10B-C8546E649EAE@gmail.com> Mime-Version: 1.0 (Mac OS X Mail 11.5 \(3445.9.1\)) Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: quoted-printable Return-path: Received: from eggs.gnu.org ([2001:4830:134:3::10]:35953) by lists.gnu.org with esmtp (Exim 4.71) (envelope-from ) id 1gHhWD-00077N-NX for emacs-orgmode@gnu.org; Tue, 30 Oct 2018 23:50:10 -0400 Received: from Debian-exim by eggs.gnu.org with spam-scanned (Exim 4.71) (envelope-from ) id 1gHhWD-0003q3-0N for emacs-orgmode@gnu.org; Tue, 30 Oct 2018 23:50:09 -0400 Received: from mail-pg1-x52f.google.com ([2607:f8b0:4864:20::52f]:43666) by eggs.gnu.org with esmtps (TLS1.0:RSA_AES_128_CBC_SHA1:16) (Exim 4.71) (envelope-from ) id 1gHhWC-0003od-Oi for emacs-orgmode@gnu.org; Tue, 30 Oct 2018 23:50:08 -0400 Received: by mail-pg1-x52f.google.com with SMTP id n10-v6so6682713pgv.10 for ; Tue, 30 Oct 2018 20:50:08 -0700 (PDT) In-Reply-To: List-Id: "General discussions about Org-mode." List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: emacs-orgmode-bounces+geo-emacs-orgmode=m.gmane.org@gnu.org Sender: "Emacs-orgmode" To: Matt Price Cc: jrfilipovits@gmail.com, Org Mode Matt, > On Oct 30, 2018, at 6:26 PM, Matt Price wrote: >=20 > Hi again Chris! >=20 > OK, so I understand a little bit of this. I would like to keep all my = letters in subheadings in a single org doc, and just export once. This = version requires a fair amount of latex in every subtree. Unless I am misunderstanding, you should be able to restrict what you = export to your subtree with a C-s (C-c C-e C-s l o) and just have one = file with the Latex Headers at the top=E2=80=A6 or you can do what Tim = suggested and put it in org-latex-classes variable (but I don=E2=80=99t = know how to do that).=20 > It would be nicer if the exporter just took care of the latex for me = and I didn't have to look at it while I'm composing (I know that's not = an issue for you, Chris). =20 >=20 > Is my best option to create an export-derived-backend based on latex = (I see that's what John K has done in scimax)? Or is the preferred = method to create a new latex class (whatever that is -- really I have no = idea) and add the header and closing lines to that?=20 You don=E2=80=99t need a new class=E2=80=94 everything can be done in = article or letter, which are standard LaTeX classes. But if you want to = control formatting to any extent, you can=E2=80=99t escape having to = learn a bit of LaTeX. Stick with the standard stuff and you won=E2=80=99t = have trouble. =20 >=20 > Also... where should I go to learn more about latex (I have = beengoogling, I've found some places, am wondering what the *best* place = is)? It appears I am approaching adulthood and am ready to learn how to = use it, after years of resisting :-/ >=20 Ahhh=E2=80=A6 that way lies madness. Welcome. I would learn as little = LaTeX as necessary and allow org to do the rest. ShareLatex, Overleaf, = and StackExchange are all fine starting points ck