From: ckelty ckelty <ckelty@gmail.com>
To: Matt Price <moptop99@gmail.com>
Cc: jrfilipovits@gmail.com, Org Mode <emacs-orgmode@gnu.org>
Subject: Re: letterhead and signature in odt export
Date: Tue, 30 Oct 2018 20:50:03 -0700 [thread overview]
Message-ID: <2FD78D67-FE7A-4114-BE48-0DCE7F435E35@gmail.com> (raw)
In-Reply-To: <CAN_Dec__pvQmmoG80y4Ru3K4HeX2i4WBci+wmGr=4mh4KPRPLg@mail.gmail.com>
Matt,
> On Oct 30, 2018, at 6:26 PM, Matt Price <moptop99@gmail.com> wrote:
>
> Hi again Chris!
>
> 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… or you can do what Tim suggested and put it in org-latex-classes variable (but I don’t know how to do that).
> 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).
>
> 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?
You don’t need a new class— 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’t escape having to learn a bit of LaTeX. Stick with the standard stuff and you won’t have trouble.
>
> 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 :-/
>
Ahhh… 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
next prev parent reply other threads:[~2018-10-31 3:50 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-30 5:55 letterhead and signature in odt export Matt Price
2018-10-30 6:54 ` Eric S Fraga
2018-10-30 12:34 ` Matt Price
2018-10-30 13:28 ` Eric S Fraga
2018-10-30 14:29 ` Jeff Filipovits
2018-10-30 15:56 ` ckelty ckelty
2018-10-31 1:26 ` Matt Price
2018-10-31 1:30 ` Matt Price
2018-10-31 3:04 ` Alan L Tyree
2018-10-31 3:50 ` ckelty ckelty [this message]
2018-11-01 12:47 ` getting close on latex letterheads [was: letterhead and signature in odt export] Matt Price
2018-11-01 13:58 ` Eric S Fraga
2018-11-02 2:28 ` Matt Price
2018-10-31 14:53 ` letterhead and signature in odt export John Kitchin
2018-10-30 21:41 ` Tim Cross
2018-10-31 1:21 ` Matt Price
2018-11-01 21:11 ` Tim Cross
2018-10-30 7:31 ` Christian Moe
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=2FD78D67-FE7A-4114-BE48-0DCE7F435E35@gmail.com \
--to=ckelty@gmail.com \
--cc=emacs-orgmode@gnu.org \
--cc=jrfilipovits@gmail.com \
--cc=moptop99@gmail.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 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).